e2fsck: merge dir_info after thread finishes

[tools/e2fsprogs.git] / misc / tune2fs.8.in

diff --git a/misc/tune2fs.8.in b/misc/tune2fs.8.in
index 3cf1f5e..b963f30 100644 (file)
--- a/misc/tune2fs.8.in
+++ b/misc/tune2fs.8.in
@@ -117,6 +117,9 @@ Adjust the number of mounts after which the filesystem will be checked by
 .BR e2fsck (8).
 If
 .I max-mount-counts
 .BR e2fsck (8).
 If
 .I max-mount-counts

+is the string "random", tune2fs will use a random value between 20 and 40.
+If
+.I max-mount-counts

 is 0 or \-1, the number of times the filesystem is mounted will be disregarded
 by
 .BR e2fsck (8)
 is 0 or \-1, the number of times the filesystem is mounted will be disregarded
 by
 .BR e2fsck (8)


@@ -127,21 +130,13 @@ checked will avoid all filesystems being checked at one time
 when using journaled filesystems.
 .sp
 Mount-count-dependent checking is disabled by default to avoid
 when using journaled filesystems.
 .sp
 Mount-count-dependent checking is disabled by default to avoid

-unanticipated long reboots while e2fsck does its work.  However,
-you may wish to consider the consequences of disabling
-mount-count-dependent checking entirely.  Bad disk drives, cables,
-memory, and kernel bugs could all corrupt a filesystem without
-marking the filesystem dirty or in error.  If you are using
-journaling on your filesystem, your filesystem will
-.B never
-be marked dirty, so it will not normally be checked.  A
-filesystem error detected by the kernel will still force
-an fsck on the next reboot, but it may already be too late
-to prevent data loss at that point.
-.sp
-See also the
-.B \-i
-option for time-dependent checking.
+unanticipated long reboots while e2fsck does its work.  If you
+are concerned about file system corruptions caused by potential hardware
+problems of kernel bugs, a better solution than mount-count-dependent
+checking is to use the
+.BR e2scrub (8)
+program.  This does require placing the file system on an LVM volume,
+however.

 .TP
 .BI \-C " mount-count"
 Set the number of times the filesystem has been mounted.
 .TP
 .BI \-C " mount-count"
 Set the number of times the filesystem has been mounted.


@@ -218,6 +213,30 @@ directories.  Valid algorithms accepted are:
 and
 .IR tea .
 .TP
 and
 .IR tea .
 .TP

+.BI encoding= encoding-name
+Enable the
+.I casefold
+feature in the super block and set
+.I encoding-name
+as the encoding to be used.  If
+.I encoding-name
+is not specified, utf8 is used. The encoding cannot be altered if casefold
+was previously enabled.
+.TP
+.BI encoding_flags= encoding-flags
+Define parameters for file name character encoding operations.  If a
+flag is not changed using this parameter, its default value is used.
+.I encoding-flags
+should be a comma-separated lists of flags to be enabled.  The flags cannot be
+altered if casefold was previously enabled.
+
+The only flag that can be set right now is
+.I strict
+which means that invalid strings should be rejected by the file system.
+In the default configuration, the
+.I strict
+flag is disabled.
+.TP

 .BI mount_opts= mount_option_string
 Set a set of default mount options which will be used when the file
 system is mounted.  Unlike the bitmask-based default mount options which
 .BI mount_opts= mount_option_string
 Set a set of default mount options which will be used when the file
 system is mounted.  Unlike the bitmask-based default mount options which


@@ -357,6 +376,27 @@ and may be no more than 10,240,000 filesystem blocks.
 There must be enough free space in the filesystem to create a journal of
 that size.
 .TP
 There must be enough free space in the filesystem to create a journal of
 that size.
 .TP

+.BI fast_commit_size= fast-commit-size
+Create an additional fast commit journal area of size
+.I fast-commit-size
+kilobytes.
+This option is only valid if
+.B fast_commit
+feature is enabled
+on the file system. If this option is not specified and if
+.B fast_commit
+feature is turned on, fast commit area size defaults to
+.I journal-size
+/ 64 megabytes. The total size of the journal with
+.B fast_commit
+feature set is
+.I journal-size
++ (
+.I fast-commit-size
+* 1024) megabytes. The total journal size may be no more than
+10,240,000 filesystem blocks or half the total file system size
+(whichever is smaller).
+.TP

 .BI location =journal-location
 Specify the location of the journal.  The argument
 .I journal-location
 .BI location =journal-location
 Specify the location of the journal.  The argument
 .I journal-location


@@ -542,6 +582,11 @@ The following filesystem features can be set or cleared using
 .B 64bit
 Enable the file system to be larger than 2^32 blocks.
 .TP
 .B 64bit
 Enable the file system to be larger than 2^32 blocks.
 .TP

+.B casefold
+Enable support for file system level casefolding.
+.B Tune2fs
+currently only supports setting this filesystem feature.
+.TP

 .B dir_index
 Use hashed b-trees to speed up lookups for large directories.
 .TP
 .B dir_index
 Use hashed b-trees to speed up lookups for large directories.
 .TP


@@ -586,6 +631,10 @@ Setting the filesystem feature is equivalent to using the
 .B \-j
 option.
 .TP
 .B \-j
 option.
 .TP

+.TP
+.B fast_commit
+Enable fast commit journaling feature to improve fsync latency.
+.TP

 .B large_dir
 Increase the limit on the number of files per directory.
 .B Tune2fs
 .B large_dir
 Increase the limit on the number of files per directory.
 .B Tune2fs


@@ -630,6 +679,13 @@ Limit the number of backup superblocks to save space on large filesystems.
 .B Tune2fs
 currently only supports setting this filesystem feature.
 .TP
 .B Tune2fs
 currently only supports setting this filesystem feature.
 .TP

+.B stable_inodes
+Prevent the filesystem from being shrunk or having its UUID changed, in order to
+allow the use of specialized encryption settings that make use of the inode
+numbers and UUID.
+.B Tune2fs
+currently only supports setting this filesystem feature.
+.TP

 .B uninit_bg
 Allow the kernel to initialize bitmaps and inode tables lazily, and to
 keep a high watermark for the unused inodes in a filesystem, to reduce
 .B uninit_bg
 Allow the kernel to initialize bitmaps and inode tables lazily, and to
 keep a high watermark for the unused inodes in a filesystem, to reduce