Lines Matching full:filesystem
7 tune2fs \- adjust tunable filesystem parameters on ext2/ext3 filesystems
90 allows the system administrator to adjust various tunable filesystem
95 Adjust the number of mounts after which the filesystem will be checked by
99 is 0 or \-1, the number of times the filesystem is mounted will be disregarded
110 memory, and kernel bugs could all corrupt a filesystem without
111 marking the filesystem dirty or in error. If you are using
112 journaling on your filesystem, your filesystem will
115 filesystem error detected by the kernel will still force
124 Set the number of times the filesystem has been mounted.
130 will check the filesystem at the next reboot.
134 In all cases, a filesystem error will cause
136 to check the filesystem on the next boot.
145 Remount filesystem read-only.
152 Set extended options for the filesystem. Extended options are comma
158 Configure the filesystem for a RAID array with
160 filesystem blocks. This is the number of blocks read or written to disk
161 before moving to next disk. This mostly affects placement of filesystem
168 Configure the filesystem for a RAID array with
170 filesystem blocks per stripe. This is typically be stride-size * N, where
176 Set a flag in the filesystem superblock indicating that it may be
177 mounted using experimental kernel code, such as the ext4dev filesystem.
180 Clear the test_fs flag, indicating the filesystem should only be mounted
181 using production-level filesystem code.
188 filesystem feature from a filesystem which has
194 Removing an external journal from a filesystem which was not cleanly unmounted
196 severe data loss and filesystem corruption.
199 Set the group which can use the reserved filesystem blocks.
206 Adjust the maximal time between two filesystem checks.
221 checking of the filesystem. Failure to do so may lead to filesystem
226 Add an ext3 journal to the filesystem. If the
229 an appropriately sized journal (given the size of the filesystem)
230 stored within the filesystem. Note that you must be using a kernel
233 If this option is used to create a journal on a mounted filesystem, an
236 will be created in the top-level directory of the filesystem, as it is
237 the only safe way to create the journal inode while the filesystem is
239 delete it, or modify it while the filesystem is mounted; for this
246 except for the root filesystem, this should happen automatically and
247 naturally during the next reboot cycle. Since the root filesystem is
253 the initrd scripts will automatically convert an ext2 root filesystem
256 file specifies the ext3 filesystem for the root filesystem in order to
258 the root filesystem.
267 Create a journal stored in the filesystem of size
269 megabytes. The size of the journal must be at least 1024 filesystem blocks
271 and may be no more than 102,400 filesystem blocks.
272 There must be enough free space in the filesystem to create a journal of
276 @JDEV@Attach the filesystem to the journal block device located on
311 @JDEV@options can be given for a filesystem.
314 List the contents of the filesystem superblock.
317 Set the volume label of the filesystem.
318 Ext2 filesystem labels can be at most 16 characters long; if
334 Set the percentage of the filesystem which may only be allocated
335 by privileged processes. Reserving some number of filesystem blocks
337 to avoid filesystem fragmentation, and to allow system
341 prevented from writing to the filesystem. Normally, the default percentage
345 Set the last-mounted directory for the filesystem.
348 Set or clear the indicated default mount options in the filesystem.
360 caret character ('^') will be cleared in the filesystem's superblock;
362 character ('+') will be added to the filesystem.
369 Enable debugging code for this filesystem.
390 When the filesystem is mounted with journalling enabled, all data
392 into the main filesystem.
395 When the filesystem is mounted with journalling enabled, all data is forced
400 When the filesystem is mounted with journalling enabled, data may be
401 written into the main filesystem after its metadata has been committed
407 Set or clear the indicated filesystem features (options) in the filesystem.
408 More than one filesystem feature can be cleared or set by separating
409 features with commas. Filesystem features prefixed with a
410 caret character ('^') will be cleared in the filesystem's superblock;
411 filesystem features without a prefix character or prefixed with a plus
412 character ('+') will be added to the filesystem.
414 The following filesystem features can be set or cleared using
419 Filesystem can contain files that are greater than 2GB. (Modern kernels
429 Use a journal to ensure filesystem consistency even across unclean shutdowns.
430 Setting the filesystem feature is equivalent to using the
441 only supports clearing this filesystem feature.
449 filesystem features,
451 must be run on the filesystem to return the filesystem to a consistent state.
462 Set the number of reserved filesystem blocks.
465 Set the time the filesystem was last checked using
468 a consistent snapshot of a filesystem, and then check the filesystem
470 hardware problems, etc. If the filesystem was clean, then this option can
471 be used to set the last checked time on the original filesystem. The format
481 Set the user who can use the reserved filesystem blocks.
487 Set the universally unique identifier (UUID) of the filesystem to
498 clear the filesystem UUID
