.I \-c
Specifies that the file system should be opened in catastrophic mode, in
which the inode and group bitmaps are not read initially. This can be
-useful for filesystems with significant corruption, but because of this,
-catastrophic mode forces the filesystem to be opened read-only.
+useful for file systems with significant corruption, but because of this,
+catastrophic mode forces the file system to be opened read-only.
.TP
.I \-i
Specifies that
.I -s superblock
Causes the file system superblock to be read from the given block
number, instead of using the primary superblock (located at an offset of
-1024 bytes from the beginning of the filesystem). If you specify the
+1024 bytes from the beginning of the file system). If you specify the
.I -s
-option, you must also provide the blocksize of the filesystem via the
+option, you must also provide the blocksize of the file system via the
.I -b
option. (This
option is rarely needed; it is used primarily when the file system is
commands take a
.I filespec
as an argument to specify an inode (as opposed to a pathname)
-in the filesystem which is currently opened by
+in the file system which is currently opened by
.BR debugfs .
The
.I filespec
number surrounded by angle brackets, e.g.,
.IR <2> .
The second form is a pathname; if the pathname is prefixed by a forward slash
-('/'), then it is interpreted relative to the root of the filesystem
+('/'), then it is interpreted relative to the root of the file system
which is currently opened by
.BR debugfs .
If not, the pathname is
flag is specified, try to allocate a block if necessary.
.TP
.BI block_dump " '[ -x ] [-f filespec] block_num"
-Dump the filesystem block given by
+Dump the file system block given by
.I block_num
in hex and ASCII format to the console. If the
.I \-f
.IR filename .
.TP
.BI dirty " [-clean]"
-Mark the filesystem as dirty, so that the superblocks will be written on exit.
+Mark the file system as dirty, so that the superblocks will be written on exit.
Additionally, clear the superblock's valid flag, or set it if
.I -clean
is specified.
.IP
(Please note that the length and range of blocks for the last extent in
an interior node is an estimate by the extents library functions, and is
-not stored in filesystem data structures. Hence, the values displayed
+not stored in file system data structures. Hence, the values displayed
may not necessarily by accurate and does not indicate a problem or
corruption in the file system.)
.TP
mappings are left alone.
.TP
.BI feature " [fs_feature] [-fs_feature] ..."
-Set or clear various filesystem features in the superblock. After setting
-or clearing any filesystem features that were requested, print the current
-state of the filesystem feature set.
+Set or clear various file system features in the superblock. After setting
+or clearing any file system features that were requested, print the current
+state of the file system feature set.
.TP
.BI filefrag " [-dvr] filespec"
Print the number of contiguous extents in
.B debugfs
process to
.I directory
-on the native filesystem.
+on the native file system.
.TP
.BI list_quota " quota_type"
Display quota information for given quota type (user, group, or project).
entry to make sure it matches the inode's type.
.TP
.BI open " [-weficD] [-b blocksize] [-d image_filename] [-s superblock] [-z undo_file] device"
-Open a filesystem for editing. The
+Open a file system for editing. The
.I -f
-flag forces the filesystem to be opened even if there are some unknown
-or incompatible filesystem features which would normally
-prevent the filesystem from being opened. The
+flag forces the file system to be opened even if there are some unknown
+or incompatible file system features which would normally
+prevent the file system from being opened. The
.I -e
-flag causes the filesystem to be opened in exclusive mode. The
+flag causes the file system to be opened in exclusive mode. The
.IR -b ", " -c ", " -d ", " -i ", " -s ", " -w ", and " -D
options behave the same as the command-line options to
.BR debugfs .
and all its contents (including regular files, symbolic links, and other
directories) into the named
.IR destination ,
-which should be an existing directory on the native filesystem.
+which should be an existing directory on the native file system.
.TP
.BI rm " pathname"
Unlink
.BR set_bg .
.TP
.BI set_current_time " time"
-Set current time in seconds since Unix epoch to use when setting filesystem
+Set current time in seconds since Unix epoch to use when setting file system
fields.
.TP
.BI seti " filespec [num]"
.B show_debugfs_params
Display
.B debugfs
-parameters such as information about currently opened filesystem.
+parameters such as information about currently opened file system.
.TP
.BI show_super_stats " [-h]"
List the contents of the super block and the block group descriptors. If the
.IR filespec .
.TP
.B supported_features
-Display filesystem features supported by this version of
+Display file system features supported by this version of
.BR debugfs .
.TP
.BI testb " block [count]"
.B link
command to link the inode to the destination pathname, or use
.B e2fsck
-to check the filesystem and link all of the recovered inodes to the
+to check the file system and link all of the recovered inodes to the
lost+found directory.
.TP
.BI unlink " pathname"
.BI write " source_file out_file"
Copy the contents of
.I source_file
-into a newly-created file in the filesystem named
+into a newly-created file in the file system named
.IR out_file .
.TP
.BI zap_block " [-f filespec] [-o offset] [-l length] [-p pattern] block_num"
.SH DESCRIPTION
.B e2fsck
is used to check the ext2/ext3/ext4 family of file systems.
-For ext3 and ext4 filesystems that use a journal, if the system has been
+For ext3 and ext4 file systems that use a journal, if the system has been
shut down uncleanly without any errors, normally, after replaying the
committed transactions in the journal, the file system should be
-marked as clean. Hence, for filesystems that use journalling,
+marked as clean. Hence, for file systems that use journalling,
.B e2fsck
will normally replay the journal and exit, unless its superblock
indicates that further checking is required.
.PP
Note that in general it is not safe to run
.B e2fsck
-on mounted filesystems. The only exception is if the
+on mounted file systems. The only exception is if the
.B \-n
option is specified, and
.BR \-c ,
.I not
specified. However, even if it is safe to do so, the results printed by
.B e2fsck
-are not valid if the filesystem is mounted. If
+are not valid if the file system is mounted. If
.B e2fsck
-asks whether or not you should check a filesystem which is mounted,
+asks whether or not you should check a file system which is mounted,
the only correct answer is ``no''. Only experts who really know what
they are doing should consider answering this question in any other way.
.PP
or
.BR \-p
are specified), the program will ask the user to fix each problem found in the
-filesystem. A response of 'y' will fix the error; 'n' will leave the error
+file system. A response of 'y' will fix the error; 'n' will leave the error
unfixed; and 'a' will fix the problem and all subsequent problems; pressing
Enter will proceed with the default response, which is printed before the
question mark. Pressing Control-C terminates e2fsck immediately.
.IR superblock .
This option is normally used when the primary superblock has been
corrupted. The location of backup superblocks is dependent on the
-filesystem's blocksize, the number of blocks per group, and features
+file system's blocksize, the number of blocks per group, and features
such as
.BR sparse_super .
.IP
.B \-n
option to print out where the superblocks exist, supposing
.B mke2fs
-is supplied with arguments that are consistent with the filesystem's layout
+is supplied with arguments that are consistent with the file system's layout
(e.g. blocksize, blocks per group,
.BR sparse_super ,
etc.).
.IP
If an alternative superblock is specified and
-the filesystem is not opened read-only, e2fsck will make sure that the
+the file system is not opened read-only, e2fsck will make sure that the
primary superblock is updated appropriately upon completion of the
-filesystem check.
+file system check.
.TP
.BI \-B " blocksize"
Normally,
This option causes
.B e2fsck
to write completion information to the specified file descriptor
-so that the progress of the filesystem
+so that the progress of the file system
check can be monitored. This option is typically used by programs
which are running
.BR e2fsck .
.BR e2fsck ).
.TP
.B \-D
-Optimize directories in filesystem. This option causes e2fsck to
+Optimize directories in file system. This option causes e2fsck to
try to optimize all directories, either by reindexing them if the
-filesystem supports directory indexing, or by sorting and compressing
-directories for smaller directories, or for filesystems using
+file system supports directory indexing, or by sorting and compressing
+directories for smaller directories, or for file systems using
traditional linear directories.
.IP
Even without the
benefit from being indexed, or if the index structures are corrupted
and need to be rebuilt. The
.B \-D
-option forces all directories in the filesystem to be optimized. This can
+option forces all directories in the file system to be optimized. This can
sometimes make them a little smaller and slightly faster to search, but
in practice, you should rarely need to use this option.
.IP
.BI ea_ver= extended_attribute_version
Set the version of the extended attribute blocks which
.B e2fsck
-will require while checking the filesystem. The version number may
+will require while checking the file system. The version number may
be 1 or 2. The default extended attribute version format is 2.
.TP
.BI journal_only
.TP
.BI fragcheck
During pass 1, print a detailed report of any discontiguous blocks for
-files in the filesystem.
+files in the file system.
.TP
.BI discard
Attempt to discard free blocks and unused inode blocks after the full
-filesystem check (discarding blocks is useful on solid state devices and sparse
+file system check (discarding blocks is useful on solid state devices and sparse
/ thin-provisioned storage). Note that discard is done in pass 5 AFTER the
-filesystem has been fully checked and only if it does not contain recognizable
+file system has been fully checked and only if it does not contain recognizable
errors. However there might be cases where
.B e2fsck
does not fully recognize a problem and hence in this case this
.BI readahead_kb
Use this many KiB of memory to pre-fetch metadata in the hopes of reducing
e2fsck runtime. By default, this is set to the size of two block groups' inode
-tables (typically 4MiB on a regular ext4 filesystem); if this amount is more
+tables (typically 4MiB on a regular ext4 file system); if this amount is more
than 1/50th of total physical memory, readahead is disabled. Set this to zero
to disable readahead entirely.
.TP
.TP
.BI check_encoding
Force verification of encoded filenames in case-insensitive directories.
-This is the default mode if the filesystem has the strict flag enabled.
+This is the default mode if the file system has the strict flag enabled.
.TP
.BI unshare_blocks
-If the filesystem has shared blocks, with the shared blocks read-only feature
+If the file system has shared blocks, with the shared blocks read-only feature
enabled, then this will unshare all shared blocks and unset the read-only
feature bit. If there is not enough free space then the operation will fail.
-If the filesystem does not have the read-only feature bit, but has shared
+If the file system does not have the read-only feature bit, but has shared
blocks anyway, then this option will have no effect. Note when using this
option, if there is no free space to clone blocks, there is no prompt to
delete files and instead the operation will fail.
Force checking even if the file system seems clean.
.TP
.B \-F
-Flush the filesystem device's buffer caches before beginning. Only
+Flush the file system device's buffer caches before beginning. Only
really useful for doing
.B e2fsck
time trials.
@JDEV@.TP
@JDEV@.BI \-j " external-journal"
-@JDEV@Set the pathname where the external-journal for this filesystem can be
+@JDEV@Set the pathname where the external-journal for this file system can be
@JDEV@found.
.TP
.BI \-k
one generated by the
.BR badblocks (8)
program. Note that the block numbers are based on the blocksize
-of the filesystem. Hence,
+of the file system. Hence,
.BR badblocks (8)
-must be given the blocksize of the filesystem in order to obtain correct
+must be given the blocksize of the file system in order to obtain correct
results. As a result, it is much simpler and safer to use the
.B -c
option to
in the file are added to the bad blocks list.)
.TP
.B \-n
-Open the filesystem read-only, and assume an answer of `no' to all
+Open the file system read-only, and assume an answer of `no' to all
questions. Allows
.B e2fsck
to be used non-interactively. This option
Automatically repair ("preen") the file system. This option will cause
.B e2fsck
to automatically
-fix any filesystem problems that can be safely fixed without human
+fix any file system problems that can be safely fixed without human
intervention. If
.B e2fsck
discovers a problem which may require the system administrator
to stop displaying a completion bar or emitting progress information.
.SH REPORTING BUGS
Almost any piece of software will have bugs. If you manage to find a
-filesystem which causes
+file system which causes
.B e2fsck
to crash, or which
.B e2fsck
.B C
so that the transcript of e2fsck's output will be useful to me.)
If you
-have a writable filesystem where the transcript can be stored, the
+have a writable file system where the transcript can be stored, the
.BR script (1)
program is a handy way to save the output of
.B e2fsck
which can sent to me after being first run through
.BR uuencode (1).
The most useful data you can send to help reproduce
-the bug is a compressed raw image dump of the filesystem, generated using
+the bug is a compressed raw image dump of the file system, generated using
.BR e2image (8).
See the
.BR e2image (8)
.BR e2fsck (8).
It controls the default behavior of
.BR e2fsck (8)
-while it is checking ext2, ext3, or ext4 filesystems.
+while it is checking ext2, ext3, or ext4 file systems.
.PP
The
.I e2fsck.conf
.TP
.I [problems]
This stanza allows the administrator to reconfigure how e2fsck handles
-various filesystem inconsistencies.
+various file system inconsistencies.
@TDB_MAN_COMMENT@.TP
@TDB_MAN_COMMENT@.I [scratch_files]
@TDB_MAN_COMMENT@This stanza controls when e2fsck will attempt to use
.TP
.I allow_cancellation
If this relation is set to a boolean value of true, then if the user
-interrupts e2fsck using ^C, and the filesystem is not explicitly flagged
+interrupts e2fsck using ^C, and the file system is not explicitly flagged
as containing errors, e2fsck will exit with an exit status of 0 instead
of 32. This setting defaults to false.
.TP
This boolean relation controls whether or not
.BR e2fsck (8)
will offer to clear
-the test_fs flag if the ext4 filesystem is available on the system. It
+the test_fs flag if the ext4 file system is available on the system. It
defaults to true.
.TP
.I defer_check_on_battery
This boolean relation controls whether or not the interval between
-filesystem checks (either based on time or number of mounts) should
+file system checks (either based on time or number of mounts) should
be doubled if the system is running on battery. This setting defaults to
true.
.TP
Use this amount of memory to read in metadata blocks ahead of the main checking
thread. Setting this value to zero disables readahead entirely. By default,
this is set the size of two block groups' inode tables (typically 4MiB on a
-regular ext4 filesystem); if this amount is more than 1/50th of total physical
+regular ext4 file system); if this amount is more than 1/50th of total physical
memory, readahead is disabled.
.TP
.I report_features
Within each problem code's subsection, the following tags may be used:
.TP
.I description
-This relation allows the message which is printed when this filesystem
+This relation allows the message which is printed when this file system
inconsistency is detected to be overridden.
.TP
.I preen_ok
This boolean relation overrides the default behavior controlling
-whether this filesystem problem should be automatically fixed when
+whether this file system problem should be automatically fixed when
.B e2fsck
is running in preen mode.
.TP
.TP
.I no_ok
This boolean relation overrides the default behavior determining
-whether or not the filesystem will be marked as inconsistent if the user
+whether or not the file system will be marked as inconsistent if the user
declines to fix the reported problem.
.TP
.I no_default
.TP
.I preen_nomessage
This boolean relation overrides the default behavior controlling
-whether or not the description for this filesystem problem should
+whether or not the description for this file system problem should
be suppressed when
.B e2fsck
is running in preen mode.
.TP
.I no_nomsg
This boolean relation overrides the default behavior controlling
-whether or not the description for this filesystem problem should
+whether or not the description for this file system problem should
be suppressed when a problem forced not to be fixed, either because
.B e2fsck
is run with the
@TDB_MAN_COMMENT@.TP
@TDB_MAN_COMMENT@.I numdirs_threshold
@TDB_MAN_COMMENT@If this relation is set, then in-memory data structures
-@TDB_MAN_COMMENT@will be used if the number of directories in the filesystem
+@TDB_MAN_COMMENT@will be used if the number of directories in the file system
@TDB_MAN_COMMENT@are fewer than amount specified.
@TDB_MAN_COMMENT@.TP
@TDB_MAN_COMMENT@.I dirinfo
The current year (i.e., 2012).
.SH EXAMPLES
The following recipe will prevent e2fsck from aborting during the boot
-process when a filesystem contains orphaned files. (Of course, this is
+process when a file system contains orphaned files. (Of course, this is
not always a good idea, since critical files that are needed for the
security of the system could potentially end up in lost+found, and
starting the system without first having a system administrator check
in an
.B editor
for the
-.B second extended filesystem.
-Its aim is to show you the various internal filesystem structures in an
+.B second extended file system.
+Its aim is to show you the various internal file system structures in an
intuitive form so that you would be able to easily understand and modify
them.
.SH DOCUMENTATION
The second article is
.B The Ext2fs overview.
-This article gives an overview of internal structure of the ext2 filesystem.
+This article gives an overview of internal structure of the ext2 file system.
You need to understand the internal layout in order to effectively edit
-your filesystem.
+your file system.
The third article is
.B EXT2ED - Design and implementation.
.SH WARNING
.B
-Do not use ext2ed on a mounted filesystem.
+Do not use ext2ed on a mounted file system.
.SH FILES
.TP
ext2ed's configuration file.
.TP
.I @datadir@/ext2.descriptors
-Definition of the various objects for the ext2 filesystem.
+Definition of the various objects for the ext2 file system.
.TP
.I /var/log/ext2ed.log
-Log file of actual changes made to the filesystem.
+Log file of actual changes made to the file system.
.TP
.I /usr/man/man8/ext2ed.8
The manual page.
The user's guide.
.TP
.I @datadir@/doc/ext2ed/Ext2fs-overview-0.1.ps
-Technical overview of the ext2 filesystem.
+Technical overview of the ext2 file system.
.TP
.I @datadir@/doc/ext2ed/ext2ed-design-0.1.ps
EXT2ED design notes.
.SH BUGS
-Filesystems bigger than 2 GB aren't yet supported.
+File Systems bigger than 2 GB aren't yet supported.
.SH AUTHOR
Gadi Oxman <tgud@tochnapc2.technion.ac.il>
.SH SEE ALSO
The
.B libblkid
library is used to identify block devices (disks) as to their content (e.g.
-filesystem type) as well as extracting additional information such as
-filesystem labels/volume names, unique identifiers/serial numbers, etc.
+file system type) as well as extracting additional information such as
+file system labels/volume names, unique identifiers/serial numbers, etc.
A common use is to allow use of LABEL= and UUID= tags instead of hard-coding
specific block device names into configuration files.
.P
in this situation.
.SH AUTHOR
.B libblkid
-was written by Andreas Dilger for the ext2 filesystem utilities, with input
+was written by Andreas Dilger for the ext2 file system utilities, with input
from Ted Ts'o. The library was subsequently heavily modified by Ted Ts'o.
.SH FILES
.TP
.B mke2fs
programs, it is important that the block size is properly specified,
since the block numbers which are generated are very dependent on the
-block size in use by the filesystem.
+block size in use by the file system.
For this reason, it is strongly recommended that
users
.B not
.B \-f
Normally, badblocks will refuse to do a read/write or a non-destructive
test on a device which is mounted, since either can cause the system to
-potentially crash and/or damage the filesystem even if it is mounted
+potentially crash and/or damage the file system even if it is mounted
read-only. This can be overridden using the
.B \-f
flag, but should almost never be used --- if you think you're smarter
option of
.BR dumpe2fs (8)
can be used to retrieve the list of blocks currently marked bad on
-an existing filesystem, in a format suitable for use with this option.
+an existing file system, in a format suitable for use with this option.
.TP
.B \-n
Use non-destructive read-write mode. By default only a non-destructive
.B blkid
program is the command-line interface to working with
.BR libblkid (3)
-library. It can determine the type of content (e.g. filesystem, swap)
+library. It can determine the type of content (e.g. file system, swap)
a block device holds, and also attributes (tokens, NAME=value pairs)
from the content metadata (e.g. LABEL or UUID fields).
.PP
inline data (N),
and verity (V).
.PP
-Not all flags are supported or utilized by all filesystems; refer to
-filesystem-specific man pages such as
+Not all flags are supported or utilized by all file systems; refer to
+file system-specific man pages such as
.BR btrfs (5),
.BR ext4 (5),
and
.BR xfs (5)
-for more filesystem-specific details.
+for more file system-specific details.
.SH OPTIONS
.TP
.B \-R
.TP
.B E
A file, directory, or symlink with the 'E' attribute set is encrypted by the
-filesystem. This attribute may not be set or cleared using
+file system. This attribute may not be set or cleared using
.BR chattr (1),
although it can be displayed by
.BR lsattr (1).
A file with the 'j' attribute has all of its data written to the ext3 or
ext4 journal before being written to the file itself, if the file system
is mounted with the "data=ordered" or "data=writeback" options and the
-file system has a journal. When the filesystem is mounted with the
+file system has a journal. When the file system is mounted with the
"data=journal" option all file data is already journalled and this
attribute has no effect. Only the superuser or a process possessing the
CAP_SYS_RESOURCE capability can set or clear this attribute.
.TP
.B t
A file with the 't' attribute will not have a partial block fragment at
-the end of the file merged with other files (for those filesystems which
+the end of the file merged with other files (for those file systems which
support tail-merging). This is necessary for applications such as LILO
-which read the filesystem directly, and which don't understand tail-merged
-files. Note: As of this writing, the ext2, ext3, and ext4 filesystems do
+which read the file system directly, and which don't understand tail-merged
+files. Note: As of this writing, the ext2, ext3, and ext4 file systems do
not support tail-merging.
.TP
.B T
.TP
.B V
A file with the 'V' attribute set has fs-verity enabled. It cannot be
-written to, and the filesystem will automatically verify all data read
+written to, and the file system will automatically verify all data read
from it against a cryptographic hash that covers the entire file's
contents, e.g. via a Merkle tree. This makes it possible to efficiently
authenticate the file. This attribute may not be set or cleared using
maintained by Theodore Ts'o <tytso@alum.mit.edu>.
.SH BUGS AND LIMITATIONS
The 'c', 's', and 'u' attributes are not honored
-by the ext2, ext3, and ext4 filesystems as implemented in the current
+by the ext2, ext3, and ext4 file systems as implemented in the current
mainline Linux kernels.
Setting 'a' and 'i' attributes will not affect the ability to write
to already existing file descriptors.
.\"
.TH DUMPE2FS 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
.SH NAME
-dumpe2fs \- dump ext2/ext3/ext4 filesystem information
+dumpe2fs \- dump ext2/ext3/ext4 file system information
.SH SYNOPSIS
.B dumpe2fs
[
.I device
.SH DESCRIPTION
.B dumpe2fs
-prints the super block and blocks group information for the filesystem
+prints the super block and blocks group information for the file system
present on
.I device.
.PP
.B Note:
-When used with a mounted filesystem, the printed
+When used with a mounted file system, the printed
information may be old or inconsistent.
.SH OPTIONS
.TP
.B \-b
-print the blocks which are reserved as bad in the filesystem.
+print the blocks which are reserved as bad in the file system.
.TP
.B \-o superblock=\fIsuperblock
use the block
.I superblock
-when examining the filesystem.
-This option is not usually needed except by a filesystem wizard who
-is examining the remains of a very badly corrupted filesystem.
+when examining the file system.
+This option is not usually needed except by a file system wizard who
+is examining the remains of a very badly corrupted file system.
.TP
.B \-o blocksize=\fIblocksize
use blocks of
.I blocksize
-bytes when examining the filesystem.
-This option is not usually needed except by a filesystem wizard who
-is examining the remains of a very badly corrupted filesystem.
+bytes when examining the file system.
+This option is not usually needed except by a file system wizard who
+is examining the remains of a very badly corrupted file system.
.TP
.B \-f
-force dumpe2fs to display a filesystem even though it may have some
-filesystem feature flags which dumpe2fs may not understand (and which
+force dumpe2fs to display a file system even though it may have some
+file system feature flags which dumpe2fs may not understand (and which
can cause some of dumpe2fs's display to be suspect).
.TP
.B \-g
group descriptor detail information.
.TP
.B \-i
-display the filesystem data from an image file created by
+display the file system data from an image file created by
.BR e2image ,
using
.I device
.B \-m
If the
.B mmp
-feature is enabled on the filesystem, check if
+feature is enabled on the file system, check if
.I device
is in use by another node, see
.BR e2mmpstatus (8)
.B -m
is specified.
.SH BUGS
-You may need to know the physical filesystem structure to understand the
+You may need to know the physical file system structure to understand the
output.
.SH AUTHOR
.B dumpe2fs
.B e2freefrag
is used to report free space fragmentation on ext2/3/4 file systems.
.I filesys
-is the filesystem device name (e.g.
+is the file system device name (e.g.
.IR /dev/hdc1 ", " /dev/md0 ).
The
.B e2freefrag
free blocks of size and of alignment
.I chunk_kb
is reported. It also displays the minimum/maximum/average free chunk size in
-the filesystem, along with a histogram of all free chunks. This information
-can be used to gauge the level of free space fragmentation in the filesystem.
+the file system, along with a histogram of all free chunks. This information
+can be used to gauge the level of free space fragmentation in the file system.
.SH OPTIONS
.TP
.BI \-c " chunk_kb"
will print how many free chunks of size
.I chunk_kb
are available in units of kilobytes (Kb). The chunk size must be a
-power of two and be larger than filesystem block size.
+power of two and be larger than file system block size.
.TP
.B \-h
Print the usage of the program.
.\"
.TH E2IMAGE 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
.SH NAME
-e2image \- Save critical ext2/ext3/ext4 filesystem metadata to a file
+e2image \- Save critical ext2/ext3/ext4 file system metadata to a file
.SH SYNOPSIS
.B e2image
.SH DESCRIPTION
The
.B e2image
-program will save critical ext2, ext3, or ext4 filesystem metadata located on
+program will save critical ext2, ext3, or ext4 file system metadata located on
.I device
to a file specified by
.IR image-file .
by using the
.B \-i
option to those programs. This can assist an expert in recovering
-catastrophically corrupted filesystems.
+catastrophically corrupted file systems.
.PP
-It is a very good idea to create image files for all filesystems on a
+It is a very good idea to create image files for all file systems on a
system and save the partition layout (which can be generated using the
.B fdisk \-l
command) at regular intervals --- at boot time, and/or every week or so.
-The image file should be stored on some filesystem other than
-the filesystem whose data it contains, to ensure that this data is
-accessible in the case where the filesystem has been badly damaged.
+The image file should be stored on some file system other than
+the file system whose data it contains, to ensure that this data is
+accessible in the case where the file system has been badly damaged.
.PP
To save disk space,
.B e2image
This does not apply to the QCOW2 image, which is not sparse.
.PP
The size of an ext2 image file depends primarily on the size of the
-filesystems and how many inodes are in use. For a typical 10 Gigabyte
-filesystem, with 200,000 inodes in use out of 1.2 million inodes, the image
-file will be approximately 35 Megabytes; a 4 Gigabyte filesystem with 15,000
+file systems and how many inodes are in use. For a typical 10 Gigabyte
+file system, with 200,000 inodes in use out of 1.2 million inodes, the image
+file will be approximately 35 Megabytes; a 4 Gigabyte file system with 15,000
inodes in use out of 550,000 inodes will result in a 3 Megabyte image file.
Image files tend to be quite compressible; an image file taking up 32 Megabytes
of space on disk will generally compress down to 3 or 4 Megabytes.
formats. In conjunction with the
.B \-r
option it is possible to clone all and only the used blocks of one
-filesystem to another device/image file.
+file system to another device/image file.
.TP
.BI \-b " superblock"
Get image from partition with broken primary superblock by using
-the superblock located at filesystem block number
+the superblock located at file system block number
.IR superblock .
The partition is copied as-is including broken primary superblock.
.TP
.BI \-B " blocksize"
-Set the filesystem blocksize in bytes. Normally,
+Set the file system blocksize in bytes. Normally,
.B e2image
will search for the superblock at various different block sizes in an
attempt to find the appropriate blocksize. This search can be fooled in
writes to reduce write wear on the device).
.TP
.B \-f
-Override the read-only requirement for the source filesystem when saving
+Override the read-only requirement for the source file system when saving
the image file using the
.B \-r
and
.B \-Q
-options. Normally, if the source filesystem is in use, the resulting image
+options. Normally, if the source file system is in use, the resulting image
file is very likely not going to be useful. In some cases where the source
-filesystem is in constant use this may be better than no image at all.
+file system is in constant use this may be better than no image at all.
.TP
.B \-I
install the metadata stored in the image file back to the device.
-It can be used to restore the filesystem metadata back to the device
+It can be used to restore the file system metadata back to the device
in emergency situations.
.PP
.B WARNING!!!!
The
.B \-I
option should only be used as a desperation measure when other
-alternatives have failed. If the filesystem has changed since the image
+alternatives have failed. If the file system has changed since the image
file was created, data
.B will
be lost. In general, you should make another full image backup of the
-filesystem first, in case you wish to try other recovery strategies afterward.
+file system first, in case you wish to try other recovery strategies afterward.
.TP
.B \-n
Cause all image writes to be skipped, and instead only print the block
.B \-s
Scramble directory entries and zero out unused portions of the directory
blocks in the written image file to avoid revealing information about
-the contents of the filesystem. However, this will prevent analysis of
+the contents of the file system. However, this will prevent analysis of
problems related to hash-tree indexed directories.
.SH RAW IMAGE FILES
The
.B \-r
option will create a raw image file, which differs
-from a normal image file in two ways. First, the filesystem metadata is
+from a normal image file in two ways. First, the file system metadata is
placed in the same relative offset within
.I image-file
as it is in the
created as a sparse file. (Beware of copying or
compressing/decompressing this file with utilities that don't understand
how to create sparse files; the file will become as large as the
-filesystem itself!) Secondly, the raw image file also includes indirect
+file system itself!) Secondly, the raw image file also includes indirect
blocks and directory blocks, which the standard image file does not have.
.PP
-Raw image files are sometimes used when sending filesystems to the maintainer
+Raw image files are sometimes used when sending file systems to the maintainer
as part of bug reports to e2fsprogs. When used in this capacity, the
recommended command is as follows (replace
.B hda1
.PP
This will only send the metadata information, without any data blocks.
However, the filenames in the directory blocks can still reveal
-information about the contents of the filesystem that the bug reporter
+information about the contents of the file system that the bug reporter
may wish to keep confidential. To address this concern, the
.B \-s
option can be specified to scramble the filenames in the image.
used by the image by storing it in special format which packs data closely
together, hence avoiding holes while still minimizing size.
.PP
-In order to send filesystem to the maintainer as a part of bug report to
+In order to send file system to the maintainer as a part of bug report to
e2fsprogs, use following commands (replace
.B hda1
with the appropriate device for your system):
.B RAW IMAGE FILES
the
.B \-s
-option can be specified to scramble the filesystem names in the image.
+option can be specified to scramble the file system names in the image.
.PP
Note that the QCOW2 image created by
.B e2image
Note that this may not work with QCOW2 images not generated by e2image.
.SH OFFSETS
-Normally a filesystem starts at the beginning of a partition, and
+Normally a file system starts at the beginning of a partition, and
.B e2image
is run on the partition. When working with image files, you don't
have the option of using the partition device, so you can specify
-the offset where the filesystem starts directly with the
+the offset where the file system starts directly with the
.B \-o
option. Similarly the
.B \-O
option specifies the offset that should be seeked to in the destination
-before writing the filesystem.
+before writing the file system.
.PP
For example, if you have a
.B dd
\ \fBe2image \-aro 1048576 img /dev/sda1\fR
.br
.PP
-Or you can clone a filesystem from a block device into an image file,
+Or you can clone a file system from a block device into an image file,
leaving room in the first MiB for a partition table with:
.PP
.br
.br
.PP
If you specify at least one offset, and only one file, an in-place
-move will be performed, allowing you to safely move the filesystem
+move will be performed, allowing you to safely move the file system
from one offset to another.
.SH AUTHOR
.\"
.TH E2LABEL 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
.SH NAME
-e2label \- Change the label on an ext2/ext3/ext4 filesystem
+e2label \- Change the label on an ext2/ext3/ext4 file system
.SH SYNOPSIS
.B e2label
.I device
.SH DESCRIPTION
.B e2label
will display or change the volume label on the ext2, ext3, or ext4
-filesystem located on
+file system located on
.I device.
.PP
If the optional argument
.\"
.TH E2MMPSTATUS 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
.SH NAME
-e2mmpstatus \- Check MMP status of an ext4 filesystem
+e2mmpstatus \- Check MMP status of an ext4 file system
.SH SYNOPSIS
.BR e2mmpstatus " [" \-i ]
-.RI < filesystem >
+.RI < file system >
.SH OPTIONS
.TP
.B \-i
.SH DESCRIPTION
.B e2mmpstatus
is used to check Multiple-Mount Protection (MMP) status of an ext4
-filesystem with the
+file system with the
.B mmp
feature enabled. The specified
-.I filesystem
+.I file system
can be a device name (e.g.
.IR /dev/hdc1 ", " /dev/sdb2 ),
-or an ext4 filesystem label or UUID, for example
+or an ext4 file system label or UUID, for example
.B UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd
or
.BR LABEL=root .
By default, the
.B e2mmpstatus
-program checks whether it is safe to mount the filesystem without taking
+program checks whether it is safe to mount the file system without taking
the risk of mounting it more than once.
.PP
MMP (multiple-mount protection) is a feature that adds protection against
-the filesystem being modified simultaneously by more than one node.
-It is NOT safe to mount a filesystem when one of the following conditions
+the file system being modified simultaneously by more than one node.
+It is NOT safe to mount a file system when one of the following conditions
is true:
.br
- 1. e2fsck is running on the filesystem.
+ 1. e2fsck is running on the file system.
.br
- 2. the filesystem is in use by another node.
+ 2. the file system is in use by another node.
.br
3. The MMP block is corrupted or cannot be read for some reason.
.br
.SH EXIT CODE
The exit code returned by
.B e2mmpstatus
-is 0 when it is safe to mount the filesystem, 1 when the MMP block shows
-the filesystem is in use on another node and it is NOT safe to mount
-the filesystem, and 2 if some other failure occurred that prevents the
+is 0 when it is safe to mount the file system, 1 when the MMP block shows
+the file system is in use on another node and it is NOT safe to mount
+the file system, and 2 if some other failure occurred that prevents the
check from properly detecting the current MMP status.
.SH SEE ALSO
.BR dumpe2fs (8),
.\"
.TH E2UNDO 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
.SH NAME
-e2undo \- Replay an undo log for an ext2/ext3/ext4 filesystem
+e2undo \- Replay an undo log for an ext2/ext3/ext4 file system
.SH SYNOPSIS
.B e2undo
[
.B e2undo
will replay the undo log
.I undo_log
-for an ext2/ext3/ext4 filesystem found on
+for an ext2/ext3/ext4 file system found on
.IR device .
This can be
used to undo a failed operation by an e2fsprogs program.
.B \-f
Normally,
.B e2undo
-will check the filesystem superblock to make sure the undo log matches
-with the filesystem on the device. If they do not match,
+will check the file system superblock to make sure the undo log matches
+with the file system on the device. If they do not match,
.B e2undo
will refuse to apply the undo log as a safety mechanism. The
.B \-f
Display a usage message.
.TP
.B \-n
-Dry-run; do not actually write blocks back to the filesystem.
+Dry-run; do not actually write blocks back to the file system.
.TP
.BI \-o " offset"
-Specify the filesystem's
+Specify the file system's
.I offset
(in bytes) from the beginning of the device or file.
.TP
.TH E4CRYPT 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
.SH NAME
-e4crypt \- ext4 filesystem encryption utility
+e4crypt \- ext4 file system encryption utility
.SH SYNOPSIS
.B e4crypt add_key -S \fR[\fB -k \fIkeyring\fR ] [\fB-v\fR] [\fB-q\fR] \fR[\fB -p \fIpad\fR ] [ \fIpath\fR ... ]
.br
.TH E4DEFRAG 8 "May 2009" "e4defrag version 2.0"
.SH NAME
-e4defrag \- online defragmenter for ext4 filesystem
+e4defrag \- online defragmenter for ext4 file system
.SH SYNOPSIS
.B e4defrag
[
.B e4defrag
reduces fragmentation of extent based file. The file targeted by
.B e4defrag
-is created on ext4 filesystem made with "-O extent" option (see
+is created on ext4 file system made with "-O extent" option (see
.BR mke2fs (8)).
The targeted file gets more contiguous blocks and improves the file access
speed.
.PP
.I target
-is a regular file, a directory, or a device that is mounted as ext4 filesystem.
+is a regular file, a directory, or a device that is mounted as ext4 file system.
If
.I target
is a directory,
.IP
Also this option outputs the average data size in one extent. If you see it,
you'll find the file has ideal extents or not. Note that the maximum extent
-size is 131072KB in ext4 filesystem (if block size is 4KB).
+size is 131072KB in ext4 file system (if block size is 4KB).
.IP
If this option is specified,
.I target
.TP
.B has_journal
.br
-Create a journal to ensure filesystem consistency even across unclean
-shutdowns. Setting the filesystem feature is equivalent to using the
+Create a journal to ensure file system consistency even across unclean
+shutdowns. Setting the file system feature is equivalent to using the
.B \-j
option with
.BR mke2fs " or " tune2fs.
.B metadata_csum
.br
This ext4 feature enables metadata checksumming. This feature stores
-checksums for all of the filesystem metadata (superblock, group
+checksums for all of the file system metadata (superblock, group
descriptor blocks, inode and block bitmaps, directories, and
extent tree blocks). The checksum algorithm used for the metadata
blocks is different than the one used for group descriptors with the
.TP
.B metadata_csum_seed
.br
-This feature allows the filesystem to store the metadata checksum seed in the
-superblock, which allows the administrator to change the UUID of a filesystem
+This feature allows the file system to store the metadata checksum seed in the
+superblock, which allows the administrator to change the UUID of a file system
using the
.B metadata_csum
feature while it is mounted.
.B mmp
.br
This ext4 feature provides multiple mount protection (MMP). MMP helps to
-protect the filesystem from being multiply mounted and is useful in
+protect the file system from being multiply mounted and is useful in
shared storage environments.
.TP
.B project
.br
This ext4 feature provides project quota support. With this feature,
-the project ID of inode will be managed when the filesystem is mounted.
+the project ID of inode will be managed when the file system is mounted.
.TP
.B quota
.br
Create quota inodes (inode #3 for userquota and inode
#4 for group quota) and set them in the superblock.
With this feature, the quotas will be enabled
-automatically when the filesystem is mounted.
+automatically when the file system is mounted.
.IP
Causes the quota files (i.e., user.quota and
group.quota which existed
By default
.B mke2fs
will attempt to reserve enough space so that the
-filesystem may grow to 1024 times its initial size. This can be changed
+file system may grow to 1024 times its initial size. This can be changed
using the
.B resize
extended option.
.TP
.B stable_inodes
.br
-Marks the filesystem's inode numbers and UUID as stable.
+Marks the file system's inode numbers and UUID as stable.
.BR resize2fs (8)
-will not allow shrinking a filesystem with this feature, nor
+will not allow shrinking a file system with this feature, nor
will
.BR tune2fs (8)
allow changing its UUID. This feature allows the use of specialized encryption
.BR mount (8)
for details.
.SH "Mount options for ext2"
-The `ext2' filesystem is the standard Linux filesystem.
+The `ext2' file system is the standard Linux file system.
Since Linux 2.5.46, for most mount options the default
-is determined by the filesystem superblock. Set them with
+is determined by the file system superblock. Set them with
.BR tune2fs (8).
.TP
.BR acl | noacl
.B minixdf
behavior is to return in the
.I f_blocks
-field the total number of blocks of the filesystem, while the
+field the total number of blocks of the file system, while the
.B bsddf
behavior (which is the default) is to subtract the overhead blocks
-used by the ext2 filesystem and not available for file storage. Thus
+used by the ext2 file system and not available for file storage. Thus
.sp 1
% mount /k \-o minixdf; df /k; umount /k
.TS
tab(#);
l2 l2 r2 l2 l2 l
l c r c c l.
-Filesystem#1024-blocks#Used#Available#Capacity#Mounted on
+File System#1024-blocks#Used#Available#Capacity#Mounted on
/dev/sda6#2630655#86954#2412169#3%#/k
.TE
.sp 1
tab(#);
l2 l2 r2 l2 l2 l
l c r c c l.
-Filesystem#1024-blocks#Used#Available#Capacity#Mounted on
+File System#1024-blocks#Used#Available#Capacity#Mounted on
/dev/sda6#2543714#13#2412169#0%#/k
.TE
.sp 1
.BR e2fsck (8)
every now and then, e.g.\& at boot time. The non-default behavior is unsupported
(check=normal and check=strict options have been removed). Note that these mount options
-don't have to be supported if ext4 kernel driver is used for ext2 and ext3 filesystems.
+don't have to be supported if ext4 kernel driver is used for ext2 and ext3 file systems.
.TP
.B debug
Print debugging info upon each (re)mount.
.TP
.BR errors= { continue | remount-ro | panic }
Define the behavior when an error is encountered.
-(Either ignore errors and just mark the filesystem erroneous and continue,
-or remount the filesystem read-only, or panic and halt the system.)
-The default is set in the filesystem superblock, and can be
+(Either ignore errors and just mark the file system erroneous and continue,
+or remount the file system read-only, or panic and halt the system.)
+The default is set in the file system superblock, and can be
changed using
.BR tune2fs (8).
.TP
.TP
.BR grpquota | noquota | quota | usrquota
The usrquota (same as quota) mount option enables user quota support on the
-filesystem. grpquota enables group quotas support. You need the quota utilities
+file system. grpquota enables group quotas support. You need the quota utilities
to actually enable and manage the quota system.
.TP
.B nouid32
Use old allocator or Orlov allocator for new inodes. Orlov is default.
.TP
\fBresgid=\fP\,\fIn\fP and \fBresuid=\fP\,\fIn\fP
-The ext2 filesystem reserves a certain percentage of the available
+The ext2 file system reserves a certain percentage of the available
space (by default 5%, see
.BR mke2fs (8)
and
.IR n .
This option is normally used when the primary superblock has been
corrupted. The location of backup superblocks is dependent on the
-filesystem's blocksize, the number of blocks per group, and features
+file system's blocksize, the number of blocks per group, and features
such as
.BR sparse_super .
.IP
.B \-n
option to print out where the superblocks exist, supposing
.B mke2fs
-is supplied with arguments that are consistent with the filesystem's layout
+is supplied with arguments that are consistent with the file system's layout
(e.g. blocksize, blocks per group,
.BR sparse_super ,
etc.).
.IP
The block number here uses 1\ k units. Thus, if you want to use logical
-block 32768 on a filesystem with 4\ k blocks, use "sb=131072".
+block 32768 on a file system with 4\ k blocks, use "sb=131072".
.TP
.BR user_xattr | nouser_xattr
Support "user." extended attributes (or not).
.SH "Mount options for ext3"
-The ext3 filesystem is a version of the ext2 filesystem which has been
+The ext3 file system is a version of the ext2 file system which has been
enhanced with journaling. It supports the same options as ext2 as
well as the following additions:
.TP
.TP
.BR norecovery / noload
Don't load the journal on mounting. Note that
-if the filesystem was not unmounted cleanly,
+if the file system was not unmounted cleanly,
skipping the journal replay will lead to the
-filesystem containing inconsistencies that can
+file system containing inconsistencies that can
lead to any number of problems.
.TP
.BR data= { journal | ordered | writeback }
Specifies the journaling mode for file data. Metadata is always journaled.
To use modes other than
.B ordered
-on the root filesystem, pass the mode to the kernel as boot parameter, e.g.\&
+on the root file system, pass the mode to the kernel as boot parameter, e.g.\&
.IR rootflags=data=journal .
.RS
.TP
.B journal
All data is committed into the journal prior to being written into the
-main filesystem.
+main file system.
.TP
.B ordered
This is the default mode. All data is forced directly out to the main file
.TP
.B writeback
Data ordering is not preserved \(en data may be written into the main
-filesystem after its metadata has been committed to the journal.
+file system after its metadata has been committed to the journal.
This is rumoured to be the highest-throughput option. It guarantees
-internal filesystem integrity, however it can allow old data to appear
+internal file system integrity, however it can allow old data to appear
in files after a crash and journal recovery.
.RE
.TP
jqfmt=vfsv1 enables journaled quotas. Journaled quotas have the advantage that
even after a crash no quota check is required. When the
.B quota
-filesystem feature is enabled, journaled quotas are used automatically, and
+file system feature is enabled, journaled quotas are used automatically, and
this mount option is ignored.
.TP
.BR usrjquota=aquota.user | grpjquota=aquota.group
usrjquota=aquota.user and grpjquota=aquota.group are required to tell the
quota system which quota database files to use. When the
.B quota
-filesystem feature is enabled, journaled quotas are used automatically, and
+file system feature is enabled, journaled quotas are used automatically, and
this mount option is ignored.
.SH "Mount options for ext4"
-The ext4 filesystem is an advanced level of the ext3 filesystem which
+The ext4 file system is an advanced level of the ext3 file system which
incorporates scalability and reliability enhancements for supporting large
-filesystem.
+file system.
The options
.B journal_dev, journal_path, norecovery, noload, data, commit, orlov,
"barrier" and "nobarrier" are added for consistency with other ext4 mount
options.
-The ext4 filesystem enables write barriers by default.
+The ext4 file system enables write barriers by default.
.TP
.BI inode_readahead_blks= n
This tuning parameter controls the maximum number of inode table blocks that
The value must be a power of 2. The default value is 32 blocks.
.TP
.BI stripe= n
-Number of filesystem blocks that mballoc will try to use for allocation size
+Number of file system blocks that mballoc will try to use for allocation size
and alignment. For RAID5/6 systems this should be the number of data disks *
-RAID chunk size in filesystem blocks.
+RAID chunk size in file system blocks.
.TP
.B delalloc
Deferring block allocation until write-out time.
to page cache.
.TP
.BI max_batch_time= usec
-Maximum amount of time ext4 should wait for additional filesystem operations to
+Maximum amount of time ext4 should wait for additional file system operations to
be batch together with a synchronous write operation. Since a synchronous
write operation is going to force a commit and then a wait for the I/O
complete, it doesn't cost much, and can be a huge throughput win, we wait for a
.B abort
Simulate the effects of calling ext4_abort() for
debugging purposes. This is normally used while
-remounting a filesystem which is already mounted.
+remounting a file system which is already mounted.
.TP
.BR auto_da_alloc | noauto_da_alloc
Many broken applications don't use fsync() when
Do not initialize any uninitialized inode table blocks in the background. This
feature may be used by installation CD's so that the install process can
complete as quickly as possible; the inode table initialization process would
-then be deferred until the next time the filesystem is mounted.
+then be deferred until the next time the file system is mounted.
.TP
.B init_itable=n
The lazy itable init code will wait n times the number of milliseconds it took
to zero out the previous block group's inode table. This minimizes the impact on
-system performance while the filesystem's inode table is being initialized.
+system performance while the file system's inode table is being initialized.
.TP
.BR discard / nodiscard
Controls whether ext4 should issue discard/TRIM commands to the underlying
.TP
.BR block_validity / noblock_validity
This option enables/disables the in-kernel facility for tracking
-filesystem metadata blocks within internal data structures. This allows multi-\c
+file system metadata blocks within internal data structures. This allows multi-\c
block allocator and other routines to quickly locate extents which might
-overlap with filesystem metadata blocks. This option is intended for debugging
+overlap with file system metadata blocks. This option is intended for debugging
purposes and since it negatively affects the performance, it is off by default.
.TP
.BR dioread_lock / dioread_nolock
use of mbcache for deduplication adds unnecessary computational overhead.
.TP
.B prjquota
-The prjquota mount option enables project quota support on the filesystem.
+The prjquota mount option enables project quota support on the file system.
You need the quota utilities to actually enable and manage the quota system.
This mount option requires the
.B project
-filesystem feature.
+file system feature.
.SH FILE ATTRIBUTES
-The ext2, ext3, and ext4 filesystems support setting the following file
+The ext2, ext3, and ext4 file systems support setting the following file
attributes on Linux systems using the
.BR chattr (1)
utility:
.sp
.BR u " - undeletable"
.sp
-In addition, the ext3 and ext4 filesystems support the following flag:
+In addition, the ext3 and ext4 file systems support the following flag:
.sp
.BR j " - data journaling"
.sp
-Finally, the ext4 filesystem also supports the following flag:
+Finally, the ext4 file system also supports the following flag:
.sp
.BR e " - extents format"
.sp
.SH DESCRIPTION
.B filefrag
reports on how badly fragmented a particular file might be. It makes
-allowances for indirect blocks for ext2 and ext3 filesystems, but can be
-used on files for any filesystem.
+allowances for indirect blocks for ext2 and ext3 file systems, but can be
+used on files for any file system.
.PP
The
.B filefrag
Use
.I blocksize
in bytes, or with [KMG] suffix, up to 1GB for output instead of the
-filesystem blocksize. For compatibility with earlier versions of
+file system blocksize. For compatibility with earlier versions of
.BR filefrag ,
if
.I blocksize
.TP
.B -P
Pre-load the ext4 extent status cache for the file. This is not
-supported on all kernels, and is only supported on ext4 filesystems.
+supported on all kernels, and is only supported on ext4 file systems.
.TP
.B \-s
Sync the file before requesting the mapping.
.\"
.TH FINDFS 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
.SH NAME
-findfs \- Find a filesystem by label or UUID
+findfs \- Find a file system by label or UUID
.SH SYNOPSIS
.B findfs
.BI LABEL= label
.BI UUID= uuid
.SH DESCRIPTION
.B findfs
-will search the disks in the system looking for a filesystem which has
+will search the disks in the system looking for a file system which has
a label matching
.I label
or a UUID equal to
.IR uuid .
-If the filesystem is found, the device name for the filesystem will
+If the file system is found, the device name for the file system will
be printed on stdout.
.PP
.SH AUTHOR
UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root).
Normally, the
.B fsck
-program will try to handle filesystems on different physical disk drives
+program will try to handle file systems on different physical disk drives
in parallel to reduce the total amount of time needed to check all of the
-filesystems.
+file systems.
.PP
-If no filesystems are specified on the command line, and the
+If no file systems are specified on the command line, and the
.B \-A
option is not specified,
.B fsck
-will default to checking filesystems in
+will default to checking file systems in
.B /etc/fstab
serially. This is equivalent to the
.B \-As
Serialize
.B fsck
operations. This is a good idea if you are checking multiple
-filesystems and the checkers are in an interactive mode. (Note:
+file systems and the checkers are in an interactive mode. (Note:
.BR e2fsck (8)
runs in an interactive mode by default. To make
.BR e2fsck (8)
.BI \-t " fslist"
Specifies the type(s) of file system to be checked. When the
.B \-A
-flag is specified, only filesystems that match
+flag is specified, only file systems that match
.I fslist
are checked. The
.I fslist
-parameter is a comma-separated list of filesystems and options
-specifiers. All of the filesystems in this comma-separated list may be
+parameter is a comma-separated list of file systems and options
+specifiers. All of the file systems in this comma-separated list may be
prefixed by a negation operator
.RB ' no '
or
.RB ' ! ',
-which requests that only those filesystems not listed in
+which requests that only those file systems not listed in
.I fslist
-will be checked. If all of the filesystems in
+will be checked. If all of the file systems in
.I fslist
-are not prefixed by a negation operator, then only those filesystems
+are not prefixed by a negation operator, then only those file systems
listed
in
.I fslist
.IR fslist .
They must have the format
.BI opts= fs-option\fR.
-If an options specifier is present, then only filesystems which contain
+If an options specifier is present, then only file systems which contain
.I fs-option
in their mount options field of
.B /etc/fstab
will be checked. If the options specifier is prefixed by a negation
operator, then only
-those filesystems that do not have
+those file systems that do not have
.I fs-option
in their mount options field of
.B /etc/fstab
.B opts=ro
appears in
.IR fslist ,
-then only filesystems listed in
+then only file systems listed in
.B /etc/fstab
with the
.B ro
For compatibility with Mandrake distributions whose boot scripts
depend upon an unauthorized UI change to the
.B fsck
-program, if a filesystem type of
+program, if a file system type of
.B loop
is found in
.IR fslist ,
.B \-t
option.
.sp
-Normally, the filesystem type is deduced by searching for
+Normally, the file system type is deduced by searching for
.I filesys
in the
.I /etc/fstab
file and using the corresponding entry.
-If the type can not be deduced, and there is only a single filesystem
+If the type can not be deduced, and there is only a single file system
given as an argument to the
.B \-t
option,
.B fsck
-will use the specified filesystem type. If this type is not
+will use the specified file system type. If this type is not
available, then the default file system type (currently ext2) is used.
.TP
.B \-A
system initialization file, instead of multiple commands for checking
a single file system.
.sp
-The root filesystem will be checked first unless the
+The root file system will be checked first unless the
.B \-P
option is specified (see below). After that,
-filesystems will be checked in the order specified by the
+file systems will be checked in the order specified by the
.I fs_passno
(the sixth) field in the
.I /etc/fstab
file.
-Filesystems with a
+File Systems with a
.I fs_passno
-value of 0 are skipped and are not checked at all. Filesystems with a
+value of 0 are skipped and are not checked at all. File Systems with a
.I fs_passno
value of greater than zero will be checked in order,
-with filesystems with the lowest
+with file systems with the lowest
.I fs_passno
number being checked first.
-If there are multiple filesystems with the same pass number,
+If there are multiple file systems with the same pass number,
fsck will attempt to check them in parallel, although it will avoid running
-multiple filesystem checks on the same physical disk.
+multiple file system checks on the same physical disk.
.sp
Hence, a very common configuration in
.I /etc/fstab
-files is to set the root filesystem to have a
+files is to set the root file system to have a
.I fs_passno
value of 1
-and to set all other filesystems to have a
+and to set all other file systems to have a
.I fs_passno
value of 2. This will allow
.B fsck
-to automatically run filesystem checkers in parallel if it is advantageous
+to automatically run file system checkers in parallel if it is advantageous
to do so. System administrators might choose
-not to use this configuration if they need to avoid multiple filesystem
+not to use this configuration if they need to avoid multiple file system
checks running in parallel for some reason --- for example, if the
machine in question is short on memory so that
excessive paging is a concern.
.TP
.B \-C\fR [ \fI "fd" \fR ]
-Display completion/progress bars for those filesystem checkers (currently
+Display completion/progress bars for those file system checkers (currently
only for ext2 and ext3) which support them. Fsck will manage the
-filesystem checkers so that only one of them will display
+file system checkers so that only one of them will display
a progress bar at a time. GUI front-ends may specify a file descriptor
.IR fd ,
in which case the progress bar information will be sent to that file descriptor.
.TP
.B \-M
-Do not check mounted filesystems and return an exit code of 0
-for mounted filesystems.
+Do not check mounted file systems and return an exit code of 0
+for mounted file systems.
.TP
.B \-N
Don't execute, just show what would be done.
.B \-P
When the
.B \-A
-flag is set, check the root filesystem in parallel with the other filesystems.
+flag is set, check the root file system in parallel with the other file systems.
This is not the safest thing in the world to do,
-since if the root filesystem is in doubt things like the
+since if the root file system is in doubt things like the
.BR e2fsck (8)
executable might be corrupted! This option is mainly provided
for those sysadmins who don't want to repartition the root
-filesystem to be small and compact (which is really the right solution).
+file system to be small and compact (which is really the right solution).
.TP
.B \-R
When checking all file systems with the
.B fs-specific-options
Options which are not understood by
.B fsck
-are passed to the filesystem-specific checker. These arguments
+are passed to the file system-specific checker. These arguments
.B must
not take arguments, as there is no
way for
file system-specific checker.
.IP
Please note that fsck is not
-designed to pass arbitrarily complicated options to filesystem-specific
+designed to pass arbitrarily complicated options to file system-specific
checkers. If you're doing something complicated, please just
-execute the filesystem-specific checker directly. If you pass
+execute the file system-specific checker directly. If you pass
.B fsck
some horribly complicated option and arguments, and it doesn't do
what you expect,
with
.BR fsck.
.PP
-Options to different filesystem-specific fsck's are not standardized.
-If in doubt, please consult the man pages of the filesystem-specific
+Options to different file system-specific fsck's are not standardized.
+If in doubt, please consult the man pages of the file system-specific
checker. Although not guaranteed, the following options are supported
by most file system checkers:
.TP
option that some file system checkers support.
.TP
.B \-n
-For some filesystem-specific checkers, the
+For some file system-specific checkers, the
.B \-n
option will cause the fs-specific fsck to avoid attempting to repair any
problems, but simply report such problems to stdout. This is however
-not true for all filesystem-specific checkers. In particular,
+not true for all file system-specific checkers. In particular,
.BR fsck.reiserfs (8)
will not report any corruption if given this option.
.BR fsck.minix (8)
option at all.
.TP
.B \-r
-Interactively repair the filesystem (ask for confirmations). Note: It
+Interactively repair the file system (ask for confirmations). Note: It
is generally a bad idea to use this option if multiple fsck's are being
run in parallel. Also note that this is
.BR e2fsck 's
reasons only.
.TP
.B \-y
-For some filesystem-specific checkers, the
+For some file system-specific checkers, the
.B \-y
option will cause the fs-specific fsck to always attempt to fix any
-detected filesystem corruption automatically. Sometimes an expert may
+detected file system corruption automatically. Sometimes an expert may
be able to do better driving the fsck manually. Note that
.B not
-all filesystem-specific checkers implement this option. In particular
+all file system-specific checkers implement this option. In particular
.BR fsck.minix (8)
and
.BR fsck.cramfs (8)
.B FSCK_FORCE_ALL_PARALLEL
If this environment variable is set,
.B fsck
-will attempt to run all of the specified filesystems in parallel,
-regardless of whether the filesystems appear to be on the same
+will attempt to run all of the specified file systems in parallel,
+regardless of whether the file systems appear to be on the same
device. (This is useful for RAID systems or high-end storage systems
such as those sold by companies such as IBM or EMC.)
.TP
.\"
.TH MKE2FS 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
.SH NAME
-mke2fs \- create an ext2/ext3/ext4 filesystem
+mke2fs \- create an ext2/ext3/ext4 file system
.SH SYNOPSIS
.B mke2fs
[
@JDEV@]
.SH DESCRIPTION
.B mke2fs
-is used to create an ext2, ext3, or ext4 filesystem, usually in a disk
+is used to create an ext2, ext3, or ext4 file system, usually in a disk
partition (or file) named by
.IR device .
.PP
.B mkfs.ext4
will create a file system for use with ext4, and so on.
.PP
-The defaults of the parameters for the newly created filesystem, if not
+The defaults of the parameters for the newly created file system, if not
overridden by the options listed below, are controlled by the
.B /etc/mke2fs.conf
configuration file. See the
.BI \-b " block-size"
Specify the size of blocks in bytes. Valid block-size values are powers of two
from 1024 up to 65536 (however note that the kernel is able to mount only
-filesystems with block-size smaller or equal to the system page size - 4k on
+file systems with block-size smaller or equal to the system page size - 4k on
x86 systems, up to 64k on ppc64 or aarch64 depending on kernel configuration).
-If omitted, block-size is heuristically determined by the filesystem size and
-the expected usage of the filesystem (see the
+If omitted, block-size is heuristically determined by the file system size and
+the expected usage of the file system (see the
.B \-T
option). In most common cases, the default block size is 4k. If
.I block-size
test is used instead of a fast read-only test.
.TP
.B \-C " cluster-size"
-Specify the size of cluster in bytes for filesystems using the bigalloc
+Specify the size of cluster in bytes for file systems using the bigalloc
feature. Valid cluster-size values are from 2048 to 256M bytes per
cluster. This can only be specified if the bigalloc feature is
enabled. (See the
.TP
.BI \-d " root-directory"
Copy the contents of the given directory into the root directory of the
-filesystem.
+file system.
.TP
.B \-D
Use direct I/O when writing to the disk. This avoids mke2fs dirtying a
.TP
.BI \-e " error-behavior"
Change the behavior of the kernel code when errors are detected.
-In all cases, a filesystem error will cause
+In all cases, a file system error will cause
.BR e2fsck (8)
-to check the filesystem on the next boot.
+to check the file system on the next boot.
.I error-behavior
can be one of the following:
.RS 1.2i
Continue normal execution.
.TP
.B remount-ro
-Remount filesystem read-only.
+Remount file system read-only.
.TP
.B panic
Cause a kernel panic.
.RE
.TP
.BI \-E " extended-options"
-Set extended options for the filesystem. Extended options are comma
+Set extended options for the file system. Extended options are comma
separated, and may take an argument using the equals ('=') sign. The
.B \-E
option used to be
feature be enabled.
.TP
.BI stride= stride-size
-Configure the filesystem for a RAID array with
+Configure the file system for a RAID array with
.I stride-size
-filesystem blocks. This is the number of blocks read or written to disk
+file system blocks. This is the number of blocks read or written to disk
before moving to the next disk, which is sometimes referred to as the
.I chunk size.
-This mostly affects placement of filesystem metadata like bitmaps at
+This mostly affects placement of file system metadata like bitmaps at
.B mke2fs
time to avoid placing them on a single disk, which can hurt performance.
It may also be used by the block allocator.
.TP
.BI stripe_width= stripe-width
-Configure the filesystem for a RAID array with
+Configure the file system for a RAID array with
.I stripe-width
-filesystem blocks per stripe. This is typically stride-size * N, where
+file system blocks per stripe. This is typically stride-size * N, where
N is the number of data-bearing disks in the RAID (e.g. for RAID 5 there is one
parity disk, so N will be the number of disks in the array minus 1).
This allows the block allocator to prevent read-modify-write of the
parity in a RAID stripe if possible when the data is written.
.TP
.BI offset= offset
-Create the filesystem at an offset from the beginning of the device or
+Create the file system at an offset from the beginning of the device or
file. This can be useful when creating disk images for virtual machines.
.TP
.BI resize= max-online-resize
Reserve enough space so that the block group descriptor table can grow
-to support a filesystem that has
+to support a file system that has
.I max-online-resize
blocks.
.TP
If enabled and the uninit_bg feature is enabled, the inode table will
not be fully initialized by
.BR mke2fs .
-This speeds up filesystem
+This speeds up file system
initialization noticeably, but it requires the kernel to finish
-initializing the filesystem in the background when the filesystem is
+initializing the file system in the background when the file system is
first mounted. If the option value is omitted, it defaults to 1 to
enable lazy inode table zeroing.
.TP
.B lazy_journal_init\fR[\fB= \fI<0 to disable, 1 to enable>\fR]
If enabled, the journal inode will not be fully zeroed out by
.BR mke2fs .
-This speeds up filesystem initialization noticeably, but carries some
+This speeds up file system initialization noticeably, but carries some
small risk if the system crashes before the journal has been overwritten
entirely one time. If the option value is omitted, it defaults to 1 to
enable lazy journal inode zeroing.
set by default to the UID and GID of the user running the mke2fs command.
The \fBroot_owner=\fR option allows explicitly specifying these values,
and avoid side-effects for users that do not expect the contents of the
-filesystem to change based on the user running \fBmke2fs\fR.
+file system to change based on the user running \fBmke2fs\fR.
.TP
.B test_fs
-Set a flag in the filesystem superblock indicating that it may be
-mounted using experimental kernel code, such as the ext4dev filesystem.
+Set a flag in the file system superblock indicating that it may be
+mounted using experimental kernel code, such as the ext4dev file system.
.TP
.B discard
Attempt to discard blocks at mkfs time (discarding blocks initially is useful
on solid state devices and sparse / thin-provisioned storage). When the device
advertises that discard also zeroes data (any subsequent read after the discard
and before write returns zero), then mark all not-yet-zeroed inode tables as
-zeroed. This significantly speeds up filesystem initialization. This is set
+zeroed. This significantly speeds up file system initialization. This is set
as default.
.TP
.B nodiscard
.B \-F
Force
.B mke2fs
-to create a filesystem, even if the specified device is not a partition
+to create a file system, even if the specified device is not a partition
on a block special device, or if other parameters do not make sense.
In order to force
.B mke2fs
-to create a filesystem even if the filesystem appears to be in use
+to create a file system even if the file system appears to be in use
or is mounted (a truly dangerous thing to do), this option must be
specified twice.
.TP
.BI \-g " blocks-per-group"
Specify the number of blocks in a block group. There is generally no
reason for the user to ever set this parameter, as the default is optimal
-for the filesystem. (For administrators who are creating
-filesystems on RAID arrays, it is preferable to use the
+for the file system. (For administrators who are creating
+file systems on RAID arrays, it is preferable to use the
.I stride
RAID parameter as part of the
.B \-E
.BI \-G " number-of-groups"
Specify the number of block groups that will be packed together to
create a larger virtual block group (or "flex_bg group") in an
-ext4 filesystem. This improves meta-data locality and performance
+ext4 file system. This improves meta-data locality and performance
on meta-data heavy workloads. The number of groups must be a power
of 2 and may only be specified if the
.B flex_bg
-filesystem feature is enabled.
+file system feature is enabled.
.TP
.BI \-i " bytes-per-inode"
Specify the bytes/inode ratio.
bytes of space on the disk. The larger the
.I bytes-per-inode
ratio, the fewer inodes will be created. This value generally shouldn't
-be smaller than the blocksize of the filesystem, since in that case more
+be smaller than the blocksize of the file system, since in that case more
inodes would be made than can ever be used. Be warned that it is not
-possible to change this ratio on a filesystem after it is created, so be
+possible to change this ratio on a file system after it is created, so be
careful deciding the correct value for this parameter. Note that resizing
-a filesystem changes the number of inodes to maintain this ratio.
+a file system changes the number of inodes to maintain this ratio.
.TP
.BI \-I " inode-size"
Specify the size of each inode in bytes.
value must be a power of 2 larger or equal to 128. The larger the
.I inode-size
the more space the inode table will consume, and this reduces the usable
-space in the filesystem and can also negatively impact performance.
+space in the file system and can also negatively impact performance.
It is not
-possible to change this value after the filesystem is created.
+possible to change this value after the file system is created.
.IP
File systems with an inode size of 128 bytes do not support timestamps
beyond January 19, 2038. Inodes which are 256 bytes or larger will
will be 128 bytes.
.TP
.B \-j
-Create the filesystem with an ext3 journal. If the
+Create the file system with an ext3 journal. If the
.B \-J
option is not specified, the default journal parameters will be used to
-create an appropriately sized journal (given the size of the filesystem)
-stored within the filesystem. Note that you must be using a kernel
+create an appropriately sized journal (given the size of the file system)
+stored within the file system. Note that you must be using a kernel
which has ext3 support in order to actually make use of the journal.
.TP
.BI \-J " journal-options"
.RS 1.2i
.TP
.BI size= journal-size
-Create an internal journal (i.e., stored inside the filesystem) of size
+Create an internal journal (i.e., stored inside the file system) of size
.I journal-size
megabytes.
-The size of the journal must be at least 1024 filesystem blocks
+The size of the journal must be at least 1024 file system blocks
(i.e., 1MB if using 1k blocks, 4MB if using 4k blocks, etc.)
-and may be no more than 10,240,000 filesystem blocks or half the total
+and may be no more than 10,240,000 file system blocks or half the total
file system size (whichever is smaller)
.TP
.BI fast_commit_size= fast-commit-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
+10,240,000 file system blocks or half the total file system size
(whichever is smaller).
.TP
.BI location =journal-location
beginning of the file system.
@JDEV@.TP
@JDEV@.BI device= external-journal
-@JDEV@Attach the filesystem to the journal block device located on
+@JDEV@Attach the file system to the journal block device located on
@JDEV@.IR external-journal .
@JDEV@The external
@JDEV@journal must already have been created using the command
@JDEV@Note that
@JDEV@.I external-journal
@JDEV@must have been created with the
-@JDEV@same block size as the new filesystem.
+@JDEV@same block size as the new file system.
@JDEV@In addition, while there is support for attaching
-@JDEV@multiple filesystems to a single external journal,
+@JDEV@multiple file systems to a single external journal,
@JDEV@the Linux kernel and
@JDEV@.BR e2fsck (8)
@JDEV@do not currently support shared external journals yet.
@JDEV@.IP
@JDEV@Only one of the
@JDEV@.BR size " or " device
-@JDEV@options can be given for a filesystem.
+@JDEV@options can be given for a file system.
.TP
.BI \-l " filename"
Read the bad blocks list from
program.
.TP
.BI \-L " new-volume-label"
-Set the volume label for the filesystem to
+Set the volume label for the file system to
.IR new-volume-label .
The maximum length of the
volume label is 16 bytes.
.TP
.BI \-m " reserved-blocks-percentage"
-Specify the percentage of the filesystem blocks reserved for
+Specify the percentage of the file system blocks reserved for
the super-user. This avoids fragmentation, and allows root-owned
daemons, such as
.BR syslogd (8),
to continue to function correctly after non-privileged processes are
-prevented from writing to the filesystem. The default percentage
+prevented from writing to the file system. The default percentage
is 5%.
.TP
.BI \-M " last-mounted-directory"
-Set the last mounted directory for the filesystem. This might be useful
+Set the last mounted directory for the file system. This might be useful
for the sake of utilities that key off of the last mounted directory to
-determine where the filesystem should be mounted.
+determine where the file system should be mounted.
.TP
.B \-n
Causes
.B mke2fs
-to not actually create a filesystem, but display what it
-would do if it were to create a filesystem. This can be used to
+to not actually create a file system, but display what it
+would do if it were to create a file system. This can be used to
determine the location of the backup superblocks for a particular
-filesystem, so long as the
+file system, so long as the
.B mke2fs
parameters that were passed when the
-filesystem was originally created are used again. (With the
+file system was originally created are used again. (With the
.B \-n
option added, of course!)
.TP
.BI \-N " number-of-inodes"
Overrides the default calculation of the number of inodes that should be
-reserved for the filesystem (which is based on the number of blocks and
+reserved for the file system (which is based on the number of blocks and
the
.I bytes-per-inode
ratio). This allows the user to specify the number
.TP
.BI \-o " creator-os"
Overrides the default value of the "creator operating system" field of the
-filesystem. The creator field is set by default to the name of the OS the
+file system. The creator field is set by default to the name of the OS the
.B mke2fs
executable was compiled for.
.TP
.B "\-O \fR[^]\fIfeature\fR[,...]"
-Create a filesystem with the given features (filesystem options),
-overriding the default filesystem options. The features that are
+Create a file system with the given features (file system options),
+overriding the default file system options. The features that are
enabled by default are specified by the
.I base_features
relation, either in the
.I features
relation found in the
.I [fs_types]
-subsections for the filesystem and usage types. See the
+subsections for the file system and usage types. See the
.BR mke2fs.conf (5)
manual page for more details.
-The filesystem type-specific configuration setting found in the
+The file system type-specific configuration setting found in the
.I [fs_types]
section will override the global default found in
.IR [defaults] .
.sp
-The filesystem feature set will be further edited
+The file system feature set will be further edited
using either the feature set specified by this option,
or if this option is not given, by the
.I default_features
-relation for the filesystem type being created, or in the
+relation for the file system type being created, or in the
.I [defaults]
section of the configuration file.
.sp
-The filesystem feature set is comprised of a list of features, separated
+The file system feature set is comprised of a list of features, separated
by commas, that are to be enabled. To disable a feature, simply
prefix the feature name with a caret ('^') character.
Features with dependencies will not be removed successfully.
-The pseudo-filesystem feature "none" will clear all filesystem features.
+The pseudo-file system feature "none" will clear all file system features.
.TP
For more information about the features which can be set, please see
the manual page
is run in a script.
.TP
.BI \-r " revision"
-Set the filesystem revision for the new filesystem. Note that 1.2
-kernels only support revision 0 filesystems. The default is to
-create revision 1 filesystems.
+Set the file system revision for the new file system. Note that 1.2
+kernels only support revision 0 file systems. The default is to
+create revision 1 file systems.
.TP
.B \-S
Write superblock and group descriptors only. This is an extreme
.B mke2fs
that affect the on-disk layout, it is critical to specify exactly
the same format options, such as blocksize, fs-type, feature flags, and
-other tunables when using this option, or the filesystem will be further
-corrupted. In some cases, such as filesystems that have been resized,
+other tunables when using this option, or the file system will be further
+corrupted. In some cases, such as file systems that have been resized,
or have had features enabled after format time, it is impossible to
-overwrite all of the superblocks correctly, and at least some filesystem
+overwrite all of the superblocks correctly, and at least some file system
corruption will occur. It is best to run this on a full copy of the
-filesystem so other options can be tried if this doesn't work.
+file system so other options can be tried if this doesn't work.
.\" .TP
.\" .BI \-t " test"
.\" Check the device for bad blocks before creating the file system
.\" using the specified test.
.TP
.BI \-t " fs-type"
-Specify the filesystem type (i.e., ext2, ext3, ext4, etc.) that is
+Specify the file system type (i.e., ext2, ext3, ext4, etc.) that is
to be created.
If this option is not specified,
.B mke2fs
the command was run (for example, using a name of the form mkfs.ext2,
mkfs.ext3, etc.) or via a default as defined by the
.B /etc/mke2fs.conf
-file. This option controls which filesystem options are used by
+file. This option controls which file system options are used by
default, based on the
.B fstypes
configuration stanza in
.sp
If the
.B \-O
-option is used to explicitly add or remove filesystem options that
-should be set in the newly created filesystem, the
-resulting filesystem may not be supported by the requested
+option is used to explicitly add or remove file system options that
+should be set in the newly created file system, the
+resulting file system may not be supported by the requested
.IR fs-type .
(e.g., "\fBmke2fs \-t ext3 \-O extent /dev/sdXX\fR" will create a
-filesystem that is not supported by the ext3 implementation as found in
+file system that is not supported by the ext3 implementation as found in
the Linux kernel; and "\fBmke2fs \-t ext3 \-O ^has_journal /dev/hdXX\fR"
-will create a filesystem that does not have a journal and hence will not
-be supported by the ext3 filesystem code in the Linux kernel.)
+will create a file system that does not have a journal and hence will not
+be supported by the ext3 file system code in the Linux kernel.)
.TP
.BI \-T " usage-type[,...]"
-Specify how the filesystem is going to be used, so that
+Specify how the file system is going to be used, so that
.B mke2fs
-can choose optimal filesystem parameters for that use. The usage
+can choose optimal file system parameters for that use. The usage
types that are supported are defined in the configuration file
.BR /etc/mke2fs.conf .
The user may specify one or more usage types
.sp
If this option is is not specified,
.B mke2fs
-will pick a single default usage type based on the size of the filesystem to
-be created. If the filesystem size is less than 3 megabytes,
+will pick a single default usage type based on the size of the file system to
+be created. If the file system size is less than 3 megabytes,
.B mke2fs
-will use the filesystem type
+will use the file system type
.IR floppy .
-If the filesystem size is greater than or equal to 3 but less than
+If the file system size is greater than or equal to 3 but less than
512 megabytes,
.BR mke2fs (8)
-will use the filesystem type
+will use the file system type
.IR small .
-If the filesystem size is greater than or equal to 4 terabytes but less than
+If the file system size is greater than or equal to 4 terabytes but less than
16 terabytes,
.BR mke2fs (8)
-will use the filesystem type
+will use the file system type
.IR big .
-If the filesystem size is greater than or equal to 16 terabytes,
+If the file system size is greater than or equal to 16 terabytes,
.BR mke2fs (8)
-will use the filesystem type
+will use the file system type
.IR huge .
Otherwise,
.BR mke2fs (8)
-will use the default filesystem type
+will use the default file system type
.IR default .
.TP
.BI \-U " UUID"
-Set the universally unique identifier (UUID) of the filesystem to
+Set the universally unique identifier (UUID) of the file system to
.IR UUID .
The format of the UUID is a series of hex digits separated by hyphens,
like this:
.RS 1.2i
.TP
.I clear
-clear the filesystem UUID
+clear the file system UUID
.TP
.I random
generate a new randomly-generated UUID
.IR device .
.TP
.B MKE2FS_SKIP_CHECK_MSG
-If set, do not show the message of filesystem automatic check caused by
+If set, do not show the message of file system automatic check caused by
mount count or check interval.
.SH AUTHOR
This version of
.BR mke2fs (8).
It controls the default parameters used by
.BR mke2fs (8)
-when it is creating ext2, ext3, or ext4 filesystems.
+when it is creating ext2, ext3, or ext4 file systems.
.PP
The
.I mke2fs.conf
executable was compiled.
.TP
.I fs_type
-This relation specifies the default filesystem type if the user does not
+This relation specifies the default file system type if the user does not
specify it via the
.B \-t
option, or if
.BI mkfs. fs-type\fR.
If both the user and the
.B mke2fs.conf
-file do not specify a default filesystem type, mke2fs will use a
-default filesystem type of
+file do not specify a default file system type, mke2fs will use a
+default file system type of
.I ext3
if a journal was requested via a command-line option, or
.I ext2
etc.) can also be specified in the
.I defaults
stanza to specify the default value to be used if the user does not
-specify one on the command line, and the filesystem-type
+specify one on the command line, and the file system-type
specific section of the configuration file does not specify a default value.
.SH THE [fs_types] STANZA
Each tag in the
.I [fs_types]
-stanza names a filesystem type or usage type which can be specified via the
+stanza names a file system type or usage type which can be specified via the
.B \-t
or
.B \-T
.P
The
.B mke2fs
-program constructs a list of fs_types by concatenating the filesystem
+program constructs a list of fs_types by concatenating the file system
type (i.e., ext2, ext3, etc.) with the usage type list. For most
configuration options,
.B mke2fs
will look for a subsection in the
.I [fs_types]
stanza corresponding with each entry in the constructed list, with later
-entries overriding earlier filesystem or usage types.
+entries overriding earlier file system or usage types.
For
example, consider the following
.B mke2fs.conf
.P
If mke2fs started with a program name of
.BR mke2fs.ext4 ,
-then the filesystem type of ext4 will be used. If the filesystem is
+then the file system type of ext4 will be used. If the file system is
smaller than 3 megabytes, and no usage type is specified, then
.B mke2fs
will use a default
.I inode_size
relation, but since the later entries in the fs_types list supersede
earlier ones, the configuration parameter for fs_types.floppy.inode_size
-will be used, so the filesystem will have an inode size of 128.
+will be used, so the file system will have an inode size of 128.
.P
The exception to this resolution is the
.I features
tag, which specifies a set of changes to the features used by the
-filesystem, and which is cumulative. So in the above example, first
+file system, and which is cumulative. So in the above example, first
the configuration relation defaults.base_features would enable an
initial feature set with the sparse_super, filetype, resize_inode, and
dir_index features enabled. Then configuration relation
fs_types.ext4.features would enable the extents and flex_bg
features, and finally the configuration relation
fs_types.floppy.features would remove
-the resize_inode feature, resulting in a filesystem feature set
+the resize_inode feature, resulting in a file system feature set
consisting of the sparse_super, filetype, dir_index,
extents_and flex_bg features.
.P
-For each filesystem type, the following tags may be used in that
+For each file system type, the following tags may be used in that
fs_type's subsection. These tags may also be used in the
.I default
section:
.TP
.I base_features
This relation specifies the features which are initially enabled for this
-filesystem type. Only one
+file system type. Only one
.I base_features
will be used, so if there are multiple entries in the fs_types list
whose subsections define the
.BR mke2fs (8).
.TP
.I enable_periodic_fsck
-This boolean relation specifies whether periodic filesystem checks should be
+This boolean relation specifies whether periodic file system checks should be
enforced at boot time. If set to true, checks will be forced every
180 days, or after a random number of mounts. These values may
be changed later via the
.TP
.I errors
Change the behavior of the kernel code when errors are detected.
-In all cases, a filesystem error will cause
+In all cases, a file system error will cause
.BR e2fsck (8)
-to check the filesystem on the next boot.
+to check the file system on the next boot.
.I errors
can be one of the following:
.RS 1.2i
Continue normal execution.
.TP
.B remount-ro
-Remount filesystem read-only.
+Remount file system read-only.
.TP
.B panic
Cause a kernel panic.
.I features
This relation specifies a comma-separated list of features edit
requests which modify the feature set
-used by the newly constructed filesystem. The syntax is the same as the
+used by the newly constructed file system. The syntax is the same as the
.B -O
command-line option to
.BR mke2fs (8);
This boolean relation, if set to a value of true, forces
.B mke2fs
to always try to create an undo file, even if the undo file might be
-huge and it might extend the time to create the filesystem image
+huge and it might extend the time to create the file system image
because the inode table isn't being initialized lazily.
.TP
.I default_features
enabled, the inode table will
not be fully initialized by
.BR mke2fs (8).
-This speeds up filesystem
+This speeds up file system
initialization noticeably, but it requires the kernel to finish
-initializing the filesystem in the background when the filesystem is
+initializing the file system in the background when the file system is
first mounted.
.TP
.I lazy_journal_init
enabled. If lazy_journal_init is true, the journal inode will not be
fully zeroed out by
.BR mke2fs .
-This speeds up filesystem initialization noticeably, but carries some
+This speeds up file system initialization noticeably, but carries some
small risk if the system crashes before the journal has been overwritten
entirely one time.
.TP
specify one on the command line.
.TP
.I reserved_ratio
-This relation specifies the default percentage of filesystem blocks
+This relation specifies the default percentage of file system blocks
reserved for the super-user, if the user does not specify one on the command
line.
.TP
.I hash_alg
This relation specifies the default hash algorithm used for the
-new filesystems with hashed b-tree directories. Valid algorithms
+new file systems with hashed b-tree directories. Valid algorithms
accepted are:
.IR legacy ,
.IR half_md4 ,
.TP
.I flex_bg_size
This relation specifies the number of block groups that will be packed
-together to create one large virtual block group on an ext4 filesystem.
+together to create one large virtual block group on an ext4 file system.
This improves meta-data locality and performance on meta-data heavy
workloads. The number of groups must be a power of 2 and may only be
-specified if the flex_bg filesystem feature is enabled.
+specified if the flex_bg file system feature is enabled.
.TP
.I options
This relation specifies additional extended options which should be
option. This can be used to configure the default extended options used
by
.BR mke2fs (8)
-on a per-filesystem type basis.
+on a per-file system type basis.
.TP
.I discard
This boolean relation specifies whether the
.BR mke2fs (8)
-should attempt to discard device prior to filesystem creation.
+should attempt to discard device prior to file system creation.
.TP
.I cluster_size
This relation specifies the default cluster size if the bigalloc file
.TP
.I hugefiles_dir
This relation specifies the directory where huge files are created,
-relative to the filesystem root.
+relative to the file system root.
.TP
.I hugefiles_uid
This relation controls the user ownership for all of the files and
directory in the current working directory on a Linux second extended
file system. There is normally a
.I lost+found
-directory in the root directory of each filesystem.
+directory in the root directory of each file system.
.PP
.B mklost+found
pre-allocates disk blocks to the
.I lost+found
directory so that when
.BR e2fsck (8)
-is being run to recover a filesystem, it does not need to allocate blocks in
-the filesystem to store a large number of unlinked files. This ensures that
+is being run to recover a file system, it does not need to allocate blocks in
+the file system to store a large number of unlinked files. This ensures that
.B e2fsck
-will not have to allocate data blocks in the filesystem during recovery.
+will not have to allocate data blocks in the file system during recovery.
.SH OPTIONS
There are none.
.SH AUTHOR
.\"
.TH TUNE2FS 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
.SH NAME
-tune2fs \- adjust tunable filesystem parameters on ext2/ext3/ext4 filesystems
+tune2fs \- adjust tunable file system parameters on ext2/ext3/ext4 file systems
.SH SYNOPSIS
.B tune2fs
[
device
.SH DESCRIPTION
.B tune2fs
-allows the system administrator to adjust various tunable filesystem
-parameters on Linux ext2, ext3, or ext4 filesystems. The current values
+allows the system administrator to adjust various tunable file system
+parameters on Linux ext2, ext3, or ext4 file systems. The current values
of these options can be displayed by using the
.B -l
option to
.SH OPTIONS
.TP
.BI \-c " max-mount-counts"
-Adjust the number of mounts after which the filesystem will be checked by
+Adjust the number of mounts after which the file system will be checked by
.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
+is 0 or \-1, the number of times the file system is mounted will be disregarded
by
.BR e2fsck (8)
and the kernel.
.sp
-Staggering the mount-counts at which filesystems are forcibly
-checked will avoid all filesystems being checked at one time
-when using journaled filesystems.
+Staggering the mount-counts at which file systems are forcibly
+checked will avoid all file systems being checked at one time
+when using journaled file systems.
.sp
Mount-count-dependent checking is disabled by default to avoid
unanticipated long reboots while e2fsck does its work. If you
however.
.TP
.BI \-C " mount-count"
-Set the number of times the filesystem has been mounted.
+Set the number of times the file system has been mounted.
If set to a greater value than the max-mount-counts parameter
set by the
.B \-c
option,
.BR e2fsck (8)
-will check the filesystem at the next reboot.
+will check the file system at the next reboot.
.TP
.BI \-e " error-behavior"
Change the behavior of the kernel code when errors are detected.
-In all cases, a filesystem error will cause
+In all cases, a file system error will cause
.BR e2fsck (8)
-to check the filesystem on the next boot.
+to check the file system on the next boot.
.I error-behavior
can be one of the following:
.RS 1.2i
Continue normal execution.
.TP
.B remount-ro
-Remount filesystem read-only.
+Remount file system read-only.
.TP
.B panic
Cause a kernel panic.
.RE
.TP
.BI \-E " extended-options"
-Set extended options for the filesystem. Extended options are comma
+Set extended options for the file system. Extended options are comma
separated, and may take an argument using the equals ('=') sign.
The following extended options are supported:
.RS 1.2i
.B clear_mmp
Reset the MMP block (if any) back to the clean state. Use only if
absolutely certain the device is not currently mounted or being
-fscked, or major filesystem corruption can result. Needs '-f'.
+fscked, or major file system corruption can result. Needs '-f'.
.TP
.BI mmp_update_interval= interval
Adjust the initial MMP update interval to
feature be enabled.
.TP
.BI stride= stride-size
-Configure the filesystem for a RAID array with
+Configure the file system for a RAID array with
.I stride-size
-filesystem blocks. This is the number of blocks read or written to disk
-before moving to next disk. This mostly affects placement of filesystem
+file system blocks. This is the number of blocks read or written to disk
+before moving to next disk. This mostly affects placement of file system
metadata like bitmaps at
.BR mke2fs (2)
time to avoid placing them on a single disk, which can hurt the performance.
It may also be used by block allocator.
.TP
.BI stripe_width= stripe-width
-Configure the filesystem for a RAID array with
+Configure the file system for a RAID array with
.I stripe-width
-filesystem blocks per stripe. This is typically be stride-size * N, where
+file system blocks per stripe. This is typically be stride-size * N, where
N is the number of data disks in the RAID (e.g. RAID 5 N+1, RAID 6 N+2).
This allows the block allocator to prevent read-modify-write of the
parity in a RAID stripe if possible when the data is written.
.TP
.BI hash_alg= hash-alg
-Set the default hash algorithm used for filesystems with hashed b-tree
+Set the default hash algorithm used for file systems with hashed b-tree
directories. Valid algorithms accepted are:
.IR legacy ,
.IR half_md4 ,
and not at all by the ext2 and ext3 file system drivers.
.TP
.B force_fsck
-Set a flag in the filesystem superblock indicating that errors have been found.
+Set a flag in the file system superblock indicating that errors have been found.
This will force fsck to run at the next mount.
.TP
.B test_fs
-Set a flag in the filesystem superblock indicating that it may be
-mounted using experimental kernel code, such as the ext4dev filesystem.
+Set a flag in the file system superblock indicating that it may be
+mounted using experimental kernel code, such as the ext4dev file system.
.TP
.B ^test_fs
-Clear the test_fs flag, indicating the filesystem should only be mounted
-using production-level filesystem code.
+Clear the test_fs flag, indicating the file system should only be mounted
+using production-level file system code.
.RE
.TP
.B \-f
Force the tune2fs operation to complete even in the face of errors. This
option is useful when removing the
.B has_journal
-filesystem feature from a filesystem which has
+file system feature from a file system which has
an external journal (or is corrupted
such that it appears to have an external journal), but that
-external journal is not available. If the filesystem appears to require
+external journal is not available. If the file system appears to require
journal replay, the
.B \-f
flag must be specified twice to proceed.
.sp
.B WARNING:
-Removing an external journal from a filesystem which was not cleanly unmounted
+Removing an external journal from a file system which was not cleanly unmounted
without first replaying the external journal can result in
-severe data loss and filesystem corruption.
+severe data loss and file system corruption.
.TP
.BI \-g " group"
-Set the group which can use the reserved filesystem blocks.
+Set the group which can use the reserved file system blocks.
The
.I group
parameter can be a numerical gid or a group name. If a group name is given,
it is converted to a numerical gid before it is stored in the superblock.
.TP
.B \-i " \fIinterval-between-checks\fR[\fBd\fR|\fBm\fR|\fBw\fR]"
-Adjust the maximal time between two filesystem checks.
+Adjust the maximal time between two file system checks.
No suffix or
.B d
will interpret the number
extended attributes in the inode table for improved performance.
.TP
.B \-j
-Add an ext3 journal to the filesystem. If the
+Add an ext3 journal to the file system. If the
.B \-J
option is not specified, the default journal parameters will be used to create
-an appropriately sized journal (given the size of the filesystem)
-stored within the filesystem. Note that you must be using a kernel
+an appropriately sized journal (given the size of the file system)
+stored within the file system. Note that you must be using a kernel
which has ext3 support in order to actually make use of the journal.
.IP
-If this option is used to create a journal on a mounted filesystem, an
+If this option is used to create a journal on a mounted file system, an
immutable file,
.BR .journal ,
-will be created in the top-level directory of the filesystem, as it is
-the only safe way to create the journal inode while the filesystem is
+will be created in the top-level directory of the file system, as it is
+the only safe way to create the journal inode while the file system is
mounted. While the ext3 journal is visible, it is not safe to
-delete it, or modify it while the filesystem is mounted; for this
+delete it, or modify it while the file system is mounted; for this
reason the file is marked immutable.
-While checking unmounted filesystems,
+While checking unmounted file systems,
.BR e2fsck (8)
will automatically move
.B .journal
-files to the invisible, reserved journal inode. For all filesystems
-except for the root filesystem, this should happen automatically and
-naturally during the next reboot cycle. Since the root filesystem is
+files to the invisible, reserved journal inode. For all file systems
+except for the root file system, this should happen automatically and
+naturally during the next reboot cycle. Since the root file system is
mounted read-only,
.BR e2fsck (8)
must be run from a rescue floppy in order to effect this transition.
.IP
On some distributions, such as Debian, if an initial ramdisk is used,
-the initrd scripts will automatically convert an ext2 root filesystem
+the initrd scripts will automatically convert an ext2 root file system
to ext3 if the
.B /etc/fstab
-file specifies the ext3 filesystem for the root filesystem in order to
+file specifies the ext3 file system for the root file system in order to
avoid requiring the use of a rescue floppy to add an ext3 journal to
-the root filesystem.
+the root file system.
.TP
.BR \-J " journal-options"
Override the default ext3 journal parameters. Journal options are comma
.RS 1.2i
.TP
.BI size= journal-size
-Create a journal stored in the filesystem of size
+Create a journal stored in the file system of size
.I journal-size
-megabytes. The size of the journal must be at least 1024 filesystem blocks
+megabytes. The size of the journal must be at least 1024 file system blocks
(i.e., 1MB if using 1k blocks, 4MB if using 4k blocks, etc.)
-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
+and may be no more than 10,240,000 file system blocks.
+There must be enough free space in the file system to create a journal of
that size.
.TP
.BI fast_commit_size= fast-commit-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
+10,240,000 file system blocks or half the total file system size
(whichever is smaller).
.TP
.BI location =journal-location
beginning of the file system.
@JDEV@.TP
@JDEV@.BI device= external-journal
-@JDEV@Attach the filesystem to the journal block device located on
+@JDEV@Attach the file system to the journal block device located on
@JDEV@.IR external-journal .
@JDEV@The external
@JDEV@journal must have been already created using the command
@JDEV@Note that
@JDEV@.I external-journal
@JDEV@must be formatted with the same block
-@JDEV@size as filesystems which will be using it.
+@JDEV@size as file systems which will be using it.
@JDEV@In addition, while there is support for attaching
-@JDEV@multiple filesystems to a single external journal,
+@JDEV@multiple file systems to a single external journal,
@JDEV@the Linux kernel and
@JDEV@.BR e2fsck (8)
@JDEV@do not currently support shared external journals yet.
@JDEV@.IP
@JDEV@Only one of the
@JDEV@.BR size " or " device
-@JDEV@options can be given for a filesystem.
+@JDEV@options can be given for a file system.
.TP
.B \-l
-List the contents of the filesystem superblock, including the current
+List the contents of the file system superblock, including the current
values of the parameters that can be set via this program.
.TP
.BI \-L " volume-label"
-Set the volume label of the filesystem.
-Ext2 filesystem labels can be at most 16 characters long; if
+Set the volume label of the file system.
+Ext2 file system labels can be at most 16 characters long; if
.I volume-label
is longer than 16 characters,
.B tune2fs
.BR /dev/hda5 .
.TP
.BI \-m " reserved-blocks-percentage"
-Set the percentage of the filesystem which may only be allocated
-by privileged processes. Reserving some number of filesystem blocks
+Set the percentage of the file system which may only be allocated
+by privileged processes. Reserving some number of file system blocks
for use by privileged processes is done
-to avoid filesystem fragmentation, and to allow system
+to avoid file system fragmentation, and to allow system
daemons, such as
.BR syslogd (8),
to continue to function correctly after non-privileged processes are
-prevented from writing to the filesystem. Normally, the default percentage
+prevented from writing to the file system. Normally, the default percentage
of reserved blocks is 5%.
.TP
.BI \-M " last-mounted-directory"
-Set the last-mounted directory for the filesystem.
+Set the last-mounted directory for the file system.
.TP
.BR \-o " [^]\fImount-option\fR[,...]"
-Set or clear the indicated default mount options in the filesystem.
+Set or clear the indicated default mount options in the file system.
Default mount options can be overridden by mount options specified
either in
.BR /etc/fstab (5)
.IP
More than one mount option can be cleared or set by separating
features with commas. Mount options prefixed with a
-caret character ('^') will be cleared in the filesystem's superblock;
+caret character ('^') will be cleared in the file system's superblock;
mount options without a prefix character or prefixed with a plus
-character ('+') will be added to the filesystem.
+character ('+') will be added to the file system.
.IP
The following mount options can be set or cleared using
.BR tune2fs :
.RS 1.2i
.TP
.B debug
-Enable debugging code for this filesystem.
+Enable debugging code for this file system.
.TP
.B bsdgroups
Emulate BSD behavior when creating new files: they will take the group-id
older kernels which only store and expect 16-bit values.
.TP
.B journal_data
-When the filesystem is mounted with journalling enabled, all data
+When the file system is mounted with journalling enabled, all data
(not just metadata) is committed into the journal prior to being written
-into the main filesystem.
+into the main file system.
.TP
.B journal_data_ordered
-When the filesystem is mounted with journalling enabled, all data is forced
+When the file system is mounted with journalling enabled, all data is forced
directly out to the main file system prior to its metadata being committed
to the journal.
.TP
.B journal_data_writeback
-When the filesystem is mounted with journalling enabled, data may be
-written into the main filesystem after its metadata has been committed
+When the file system is mounted with journalling enabled, data may be
+written into the main file system after its metadata has been committed
to the journal. This may increase throughput, however, it may allow old
data to appear in files after a crash and journal recovery.
.TP
.RE
.TP
.BR \-O " [^]\fIfeature\fR[,...]"
-Set or clear the indicated filesystem features (options) in the filesystem.
-More than one filesystem feature can be cleared or set by separating
-features with commas. Filesystem features prefixed with a
-caret character ('^') will be cleared in the filesystem's superblock;
-filesystem features without a prefix character or prefixed with a plus
-character ('+') will be added to the filesystem. For a detailed
+Set or clear the indicated file system features (options) in the file system.
+More than one file system feature can be cleared or set by separating
+features with commas. File System features prefixed with a
+caret character ('^') will be cleared in the file system's superblock;
+file system features without a prefix character or prefixed with a plus
+character ('+') will be added to the file system. For a detailed
description of the file system features, please see the man page
.BR ext4 (5).
.IP
-The following filesystem features can be set or cleared using
+The following file system features can be set or cleared using
.BR tune2fs :
.RS 1.2i
.TP
.B casefold
Enable support for file system level casefolding.
.B Tune2fs
-currently only supports setting this filesystem feature.
+currently only supports setting this file system feature.
.TP
.B dir_index
Use hashed b-trees to speed up lookups for large directories.
separate inode if necessary, increasing the limit on the size and number of
extended attributes per file.
.B Tune2fs
-currently only supports setting this filesystem feature.
+currently only supports setting this file system feature.
.TP
.B encrypt
Enable support for file system level encryption.
.B Tune2fs
-currently only supports setting this filesystem feature.
+currently only supports setting this file system feature.
.TP
.B extent
Enable the use of extent trees to store the location of data blocks in inodes.
.B Tune2fs
-currently only supports setting this filesystem feature.
+currently only supports setting this file system feature.
.TP
.B extra_isize
Enable the extended inode fields used by ext4.
enabled.
.TP
.B has_journal
-Use a journal to ensure filesystem consistency even across unclean shutdowns.
-Setting the filesystem feature is equivalent to using the
+Use a journal to ensure file system consistency even across unclean shutdowns.
+Setting the file system feature is equivalent to using the
.B \-j
option.
.TP
.B large_dir
Increase the limit on the number of files per directory.
.B Tune2fs
-currently only supports setting this filesystem feature.
+currently only supports setting this file system feature.
.TP
.B huge_file
Support files larger than 2 terabytes in size.
.TP
.B large_file
-Filesystem can contain files that are greater than 2GB.
+File System can contain files that are greater than 2GB.
.TP
.B metadata_csum
Store a checksum to protect the contents in each metadata block.
.TP
.B metadata_csum_seed
-Allow the filesystem to store the metadata checksum seed in the
-superblock, enabling the administrator to change the UUID of a filesystem
+Allow the file system to store the metadata checksum seed in the
+superblock, enabling the administrator to change the UUID of a file system
using the
.B metadata_csum
feature while it is mounted.
Reserve space so the block group descriptor table may grow in the
future.
.B Tune2fs
-only supports clearing this filesystem feature.
+only supports clearing this file system feature.
.TP
.B sparse_super
-Limit the number of backup superblocks to save space on large filesystems.
+Limit the number of backup superblocks to save space on large file systems.
.B Tune2fs
-currently only supports setting this filesystem feature.
+currently only supports setting this file system feature.
.TP
.B stable_inodes
-Prevent the filesystem from being shrunk or having its UUID changed, in order to
+Prevent the file system 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.
+currently only supports setting this file system 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
+keep a high watermark for the unused inodes in a file system, to reduce
.BR e2fsck (8)
time. The first e2fsck run after enabling this feature will take the
full time, but subsequent e2fsck runs will take only a fraction of the
.B verity
Enable support for verity protected files.
.B Tune2fs
-currently only supports setting this filesystem feature.
+currently only supports setting this file system feature.
.RE
.IP
After setting or clearing
.BR filetype ,
or
.B resize_inode
-filesystem features,
+file system features,
the file system may require being checked using
.BR e2fsck (8)
-to return the filesystem to a consistent state.
+to return the file system to a consistent state.
.B Tune2fs
will print a message requesting that the system administrator run
.BR e2fsck (8)
feature,
.B e2fsck -D
can be run to convert existing directories to the hashed B-tree format.
-Enabling certain filesystem features may prevent the filesystem from being
+Enabling certain file system features may prevent the file system from being
mounted by kernels which do not support those features. In particular, the
.B uninit_bg
and
.B flex_bg
-features are only supported by the ext4 filesystem.
+features are only supported by the ext4 file system.
.TP
.BI \-r " reserved-blocks-count"
-Set the number of reserved filesystem blocks.
+Set the number of reserved file system blocks.
.TP
.BI \-Q " quota-options"
Sets 'quota' feature on the superblock and works on the quota files for the
.RE
.TP
.BI \-T " time-last-checked"
-Set the time the filesystem was last checked using
+Set the time the file system was last checked using
.BR e2fsck .
The time is interpreted using the current (local) timezone.
This can be useful in scripts which use a Logical Volume Manager to make
-a consistent snapshot of a filesystem, and then check the filesystem
+a consistent snapshot of a file system, and then check the file system
during off hours to make sure it hasn't been corrupted due to
-hardware problems, etc. If the filesystem was clean, then this option can
-be used to set the last checked time on the original filesystem. The format
+hardware problems, etc. If the file system was clean, then this option can
+be used to set the last checked time on the original file system. The format
of
.I time-last-checked
is the international date format, with an optional time specifier, i.e.
current time.
.TP
.BI \-u " user"
-Set the user who can use the reserved filesystem blocks.
+Set the user who can use the reserved file system blocks.
.I user
can be a numerical uid or a user name. If a user name is given, it
is converted to a numerical uid before it is stored in the superblock.
.TP
.BI \-U " UUID"
-Set the universally unique identifier (UUID) of the filesystem to
+Set the universally unique identifier (UUID) of the file system to
.IR UUID .
The format of the UUID is a series of hex digits separated by hyphens,
like this:
.RS 1.2i
.TP
.I clear
-clear the filesystem UUID
+clear the file system UUID
.TP
.I random
generate a new randomly-generated UUID
program will resize ext2, ext3, or ext4 file systems. It can be used to
enlarge or shrink an unmounted file system located on
.IR device .
-If the filesystem is mounted, it can be used to expand the size of the
-mounted filesystem, assuming the kernel and the file system supports
+If the file system is mounted, it can be used to expand the size of the
+mounted file system, assuming the kernel and the file system supports
on-line resizing. (Modern Linux 2.6 kernels will support on-line resize
for file systems mounted using ext3 and ext4; ext3 file systems will
require the use of file systems with the resize_inode feature enabled.)
.PP
The
.I size
-parameter specifies the requested new size of the filesystem.
+parameter specifies the requested new size of the file system.
If no units are specified, the units of the
.I size
-parameter shall be the filesystem blocksize of the filesystem.
+parameter shall be the file system blocksize of the file system.
Optionally, the
.I size
parameter may be suffixed by one of the following units
for power-of-two kilobytes, megabytes, gigabytes, terabytes or 512 byte
sectors respectively. The
.I size
-of the filesystem may never be larger than the size of the partition.
+of the file system may never be larger than the size of the partition.
If
.I size
parameter is not specified, it will default to the size of the partition.
The
.B resize2fs
program does not manipulate the size of partitions. If you wish to enlarge
-a filesystem, you must make sure you can expand the size of the
+a file system, you must make sure you can expand the size of the
underlying partition first. This can be done using
.BR fdisk (8)
by deleting the partition and recreating it with a larger size or using
When
recreating the partition, make sure you create it with the same starting
disk cylinder as before! Otherwise, the resize operation will
-certainly not work, and you may lose your entire filesystem.
+certainly not work, and you may lose your entire file system.
After running
.BR fdisk (8),
-run resize2fs to resize the ext2 filesystem
+run resize2fs to resize the ext2 file system
to use all of the space in the newly enlarged partition.
.PP
If you wish to shrink an ext2 partition, first use
.B resize2fs
-to shrink the size of filesystem. Then you may use
+to shrink the size of file system. Then you may use
.BR fdisk (8)
to shrink the size of the partition. When shrinking the size of
the partition, make sure you do not make it smaller than the new size
-of the ext2 filesystem!
+of the ext2 file system!
.PP
The
.B \-b
options enable and disable the 64bit feature, respectively. The resize2fs
program will, of course, take care of resizing the block group descriptors
and moving other data blocks out of the way, as needed. It is not possible
-to resize the filesystem concurrent with changing the 64bit status.
+to resize the file system concurrent with changing the 64bit status.
.SH OPTIONS
.TP
.B \-b
.br
16 \-\ Print timing information
.br
- 32 \-\ Debug minimum filesystem size (\-M) calculation
+ 32 \-\ Debug minimum file system size (\-M) calculation
.TP
.B \-f
-Forces resize2fs to proceed with the filesystem resize operation, overriding
+Forces resize2fs to proceed with the file system resize operation, overriding
some safety checks which resize2fs normally enforces.
.TP
.B \-F
-Flush the filesystem device's buffer caches before beginning. Only
+Flush the file system device's buffer caches before beginning. Only
really useful for doing
.B resize2fs
time trials.
The
.B resize2fs
program will heuristically determine the RAID stride that was specified
-when the filesystem was created. This option allows the user to
+when the file system was created. This option allows the user to
explicitly specify a RAID stride setting to be used by resize2fs instead.
.TP
.BI \-z " undo_file"
WARNING: The undo file cannot be used to recover from a power or system crash.
.SH KNOWN BUGS
-The minimum size of the filesystem as estimated by resize2fs may be
-incorrect, especially for filesystems with 1k and 2k blocksizes.
+The minimum size of the file system as estimated by resize2fs may be
+incorrect, especially for file systems with 1k and 2k blocksizes.
.SH AUTHOR
.B resize2fs
was written by Theodore Ts'o <tytso@mit.edu>.
.TH E2SCRUB 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
.SH NAME
-e2scrub - check the contents of a mounted ext[234] filesystem
+e2scrub - check the contents of a mounted ext[234] file system
.SH SYNOPSYS
.B
e2scrub [OPTION] MOUNTPOINT | DEVICE
.SH DESCRIPTION
.B e2scrub
attempts to check (but not repair) all metadata in a mounted ext[234]
-filesystem if the filesystem resides on an LVM logical volume.
+file system if the file system resides on an LVM logical volume.
The block device of the LVM logical volume can also be passed in.
This program snapshots the volume and runs a file system check on the snapshot
.B fstrim
can be called on the file system if it is mounted.
If errors are found, the file system will be marked as having errors.
-The filesystem should be taken offline and
+The file system should be taken offline and
.B e2fsck
run as soon as possible, because
.B e2scrub
does not fix corruptions.
-If the filesystem is not repaired,
+If the file system is not repaired,
.B e2fsck
will be run before the next mount.
.SH OPTIONS
Run
.B
fstrim(1)
-on the mounted filesystem if no errors are found.
+on the mounted file system if no errors are found.
.TP
\fB-V\fR
Print version information and exit.
.TH E2SCRUB 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
.SH NAME
-e2scrub_all - check all mounted ext[234] filesystems for errors.
+e2scrub_all - check all mounted ext[234] file systems for errors.
.SH SYNOPSYS
.B
e2scrub_all [OPTION]
The checking is performed by invoking the
.B e2scrub
tool, which will look for corruptions.
-Corrupt filesystems will be tagged as having errors so that fsck will be
+Corrupt file systems will be tagged as having errors so that fsck will be
invoked before the next mount.
If no errors are encountered,
.B fstrim
-will be called on the filesystem if it is mounted.
+will be called on the file system if it is mounted.
See the
.B e2scrub
manual page for more information about how the checking is performed.
Remove e2scrub snapshots but do not check anything.
.TP
\fB-A\fR
-Scrub all ext[234] filesystems even if they are not mounted.
+Scrub all ext[234] file systems even if they are not mounted.
.TP
\fB-V\fR
Print version information and exit.
git://git.whamcloud.com / tools / e2fsprogs.git / commitdiff