Lines Matching full:filesystem
50 is the device file where the filesystem is stored (e.g.
66 are not valid if the filesystem is mounted. If
68 asks whether or not you should check a filesystem which is mounted,
87 filesystem's blocksize. For filesystems with 1k blocksizes, a backup
99 which specifies blocksize of the filesystem must be specified in order
103 the filesystem is not opened read-only, e2fsck will make sure that the
105 filesystem check.
134 so that the progress of the filesystem
153 Optimize directories in filesystem. This option causes e2fsck to
155 filesystem supports directory indexing, or by sorting and compressing
168 option forces all directories in the filesystem to be optimized. This can
186 will require while checking the filesystem. The version number may
195 files in the filesystem.
199 filesystem check (discarding blocks is useful on solid state devices and sparse
201 filesystem has been fully checked and only if it does not contain recognizable
216 Flush the filesystem device's buffer caches before beginning. Only
222 @JDEV@Set the pathname where the external-journal for this filesystem can be
240 of the filesystem. Hence,
242 must be given the blocksize of the filesystem in order to obtain correct
260 Open the filesystem read-only, and assume an answer of `no' to all
274 fix any filesystem problems that can be safely fixed without human
355 filesystem which causes
376 have a writable filesystem where the transcript can be stored, the
397 the bug is a compressed raw image dump of the filesystem, generated using
