Lines Matching full:filesystem
7 tune2fs \- adjust tunable filesystem parameters on ext2/ext3/ext4 filesystems
94 allows the system administrator to adjust various tunable filesystem
112 Adjust the number of mounts after which the filesystem will be checked by
116 is 0 or \-1, the number of times the filesystem is mounted will be disregarded
127 memory, and kernel bugs could all corrupt a filesystem without
128 marking the filesystem dirty or in error. If you are using
129 journaling on your filesystem, your filesystem will
132 filesystem error detected by the kernel will still force
141 Set the number of times the filesystem has been mounted.
147 will check the filesystem at the next reboot.
151 In all cases, a filesystem error will cause
153 to check the filesystem on the next boot.
162 Remount filesystem read-only.
169 Set extended options for the filesystem. Extended options are comma
177 fscked, or major filesystem corruption can result. Needs '-f'.
190 Configure the filesystem for a RAID array with
192 filesystem blocks. This is the number of blocks read or written to disk
193 before moving to next disk. This mostly affects placement of filesystem
200 Configure the filesystem for a RAID array with
202 filesystem blocks per stripe. This is typically be stride-size * N, where
236 Set a flag in the filesystem superblock indicating that it may be
237 mounted using experimental kernel code, such as the ext4dev filesystem.
240 Clear the test_fs flag, indicating the filesystem should only be mounted
241 using production-level filesystem code.
248 filesystem feature from a filesystem which has
254 Removing an external journal from a filesystem which was not cleanly unmounted
256 severe data loss and filesystem corruption.
259 Set the group which can use the reserved filesystem blocks.
266 Adjust the maximal time between two filesystem checks.
283 checking of the filesystem. Failure to do so may lead to filesystem
288 Add an ext3 journal to the filesystem. If the
291 an appropriately sized journal (given the size of the filesystem)
292 stored within the filesystem. Note that you must be using a kernel
295 If this option is used to create a journal on a mounted filesystem, an
298 will be created in the top-level directory of the filesystem, as it is
299 the only safe way to create the journal inode while the filesystem is
301 delete it, or modify it while the filesystem is mounted; for this
308 except for the root filesystem, this should happen automatically and
309 naturally during the next reboot cycle. Since the root filesystem is
315 the initrd scripts will automatically convert an ext2 root filesystem
318 file specifies the ext3 filesystem for the root filesystem in order to
320 the root filesystem.
329 Create a journal stored in the filesystem of size
331 megabytes. The size of the journal must be at least 1024 filesystem blocks
333 and may be no more than 102,400 filesystem blocks.
334 There must be enough free space in the filesystem to create a journal of
338 @JDEV@Attach the filesystem to the journal block device located on
373 @JDEV@options can be given for a filesystem.
376 List the contents of the filesystem superblock, including the current
380 Set the volume label of the filesystem.
381 Ext2 filesystem labels can be at most 16 characters long; if
397 Set the percentage of the filesystem which may only be allocated
398 by privileged processes. Reserving some number of filesystem blocks
400 to avoid filesystem fragmentation, and to allow system
404 prevented from writing to the filesystem. Normally, the default percentage
408 Set the last-mounted directory for the filesystem.
411 Set or clear the indicated default mount options in the filesystem.
423 caret character ('^') will be cleared in the filesystem's superblock;
425 character ('+') will be added to the filesystem.
432 Enable debugging code for this filesystem.
453 When the filesystem is mounted with journalling enabled, all data
455 into the main filesystem.
458 When the filesystem is mounted with journalling enabled, all data is forced
463 When the filesystem is mounted with journalling enabled, data may be
464 written into the main filesystem after its metadata has been committed
499 Set or clear the indicated filesystem features (options) in the filesystem.
500 More than one filesystem feature can be cleared or set by separating
501 features with commas. Filesystem features prefixed with a
502 caret character ('^') will be cleared in the filesystem's superblock;
503 filesystem features without a prefix character or prefixed with a plus
504 character ('+') will be added to the filesystem. For a detailed
508 The following filesystem features can be set or cleared using
537 Use a journal to ensure filesystem consistency even across unclean shutdowns.
538 Setting the filesystem feature is equivalent to using the
546 Filesystem can contain files that are greater than 2GB.
552 only supports clearing this filesystem feature.
565 keep a high watermark for the unused inodes in a filesystem, to reduce
578 filesystem features,
580 must be run on the filesystem to return the filesystem to a consistent state.
589 Enabling certain filesystem features may prevent the filesystem from being
594 features are only supported by the ext4 filesystem.
600 Set the number of reserved filesystem blocks.
615 Set the time the filesystem was last checked using
619 a consistent snapshot of a filesystem, and then check the filesystem
621 hardware problems, etc. If the filesystem was clean, then this option can
622 be used to set the last checked time on the original filesystem. The format
632 Set the user who can use the reserved filesystem blocks.
638 Set the universally unique identifier (UUID) of the filesystem to
649 clear the filesystem UUID
