Section: Maintenance Commands (8)
Updated: January 2020
e2fsck - check a Linux ext2/ext3/ext4 file system
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
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,
will normally replay the journal and exit, unless its superblock
indicates that further checking is required.
is a block device (e.g.,
or file containing the file system.
Note that in general it is not safe to run
on mounted filesystems. The only exception is if the
option is specified, and
specified. However, even if it is safe to do so, the results printed by
are not valid if the filesystem is mounted. If
asks whether or not you should check a filesystem 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.
is run in interactive mode (meaning that none of
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
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.
This option does the same thing as the
option. It is provided for backwards compatibility only; it is
suggested that people use
option whenever possible.
- -b superblock
Instead of using the normal superblock, use an alternative 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
Additional backup superblocks can be determined by using the
program using the
option to print out where the superblocks exist, supposing
is supplied with arguments that are consistent with the filesystem's layout
(e.g. blocksize, blocks per group,
If an alternative superblock is specified and
the filesystem is not opened read-only, e2fsck will make sure that the
primary superblock is updated appropriately upon completion of the
- -B blocksize
will search for the superblock at various different
block sizes in an attempt to find the appropriate block size.
This search can be fooled in some cases. This option forces
to only try locating the superblock at a particular blocksize.
If the superblock is not found,
will terminate with a fatal error.
This option causes
program to do a read-only scan of the device in order to find any bad
blocks. If any bad blocks are found, they are added to the bad block
inode to prevent them from being allocated to a file or directory. If
this option is specified twice, then the bad block scan will be done
using a non-destructive read-write test.
- -C fd
This option causes
to write completion information to the specified file descriptor
so that the progress of the filesystem
check can be monitored. This option is typically used by programs
which are running
If the file descriptor number is negative, then absolute value of
the file descriptor will be used, and the progress information will be
suppressed initially. It can later be enabled by sending the
process a SIGUSR1 signal.
If the file descriptor specified is 0,
will print a completion bar as it goes about its business. This requires
that e2fsck is running on a video console or terminal.
Print debugging output (useless unless you are debugging
Optimize directories in filesystem. 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
traditional linear directories.
Even without the
may sometimes optimize a few directories --- for example, if
directory indexing is enabled and a directory is not indexed and would
benefit from being indexed, or if the index structures are corrupted
and need to be rebuilt. The
option forces all directories in the filesystem 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.
option will detect directory entries with duplicate names in a single
directory, which e2fsck normally does not enforce for performance reasons.
- -E extended_options
Set e2fsck extended options. Extended options are comma
separated, and may take an argument using the equals ('=') sign. The
following options are supported:
Set the version of the extended attribute blocks which
will require while checking the filesystem. The version number may
be 1 or 2. The default extended attribute version format is 2.
Only replay the journal if required, but do not perform any further checks
During pass 1, print a detailed report of any discontiguous blocks for
files in the filesystem.
Attempt to discard free blocks and unused inode blocks after the full
filesystem 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
errors. However there might be cases where
does not fully recognize a problem and hence in this case this
option may prevent you from further manual data recovery.
Do not attempt to discard free blocks and unused inode blocks. This option is
exactly the opposite of discard option. This is set as default.
Do not offer to optimize the extent tree by eliminating unnecessary
width or depth. This can also be enabled in the options section of
Offer to optimize the extent tree by eliminating unnecessary
width or depth. This is the default unless otherwise specified in
Trade off using memory for speed when checking a file system with a
large number of hard-linked files. The amount of memory required is
proportional to the number of inodes in the file system. For large file
systems, this can be gigabytes of memory. (For example, a 40TB file system
with 2.8 billion inodes will consume an additional 5.7 GB memory if this
optimization is enabled.) This optimization can also be enabled in the
options section of
optimization. This is the default unless otherwise specified in
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
than 1/50th of total physical memory, readahead is disabled. Set this to zero
to disable readahead entirely.
Convert block-mapped files to extent-mapped files.
Only fix damaged metadata; do not optimize htree directories or compress
extent trees. This option is incompatible with the -D and -E bmap2extent
If the filesystem 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
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.
Note that unshare_blocks implies the "-f" option to ensure that all passes
are run. Additionally, if "-n" is also specified, e2fsck will simulate trying
to allocate enough space to deduplicate. If this fails, the exit code will
Force checking even if the file system seems clean.
Flush the filesystem device's buffer caches before beginning. Only
really useful for doing
- -j external-journal
Set the pathname where the external-journal for this filesystem can be
When combined with the
option, any existing bad blocks in the bad blocks list are preserved,
and any new bad blocks found by running
will be added to the existing bad blocks list.
- -l filename
Add the block numbers listed in the file specified by
to the list of bad blocks. The format of this file is the same as the
one generated by the
program. Note that the block numbers are based on the blocksize
of the filesystem. Hence,
must be given the blocksize of the filesystem in order to obtain correct
results. As a result, it is much simpler and safer to use the
since it will assure that the correct parameters are passed to the
- -L filename
Set the bad blocks list to be the list of blocks specified by
(This option is the same as the
option, except the bad blocks list is cleared before the blocks listed
in the file are added to the bad blocks list.)
Open the filesystem read-only, and assume an answer of `no' to all
to be used non-interactively. This option
may not be specified at the same time as the
Automatically repair ("preen") the file system. This option will cause
fix any filesystem problems that can be safely fixed without human
discovers a problem which may require the system administrator
to take additional corrective action,
will print a description of the problem and then exit with the value 4
logically or'ed into the exit code. (See the EXIT CODE section.)
This option is normally used by the system's boot scripts. It may not
be specified at the same time as the
This option does nothing at all; it is provided only for backwards
Print timing statistics for
If this option is used twice, additional timing statistics are printed
on a pass by pass basis.
Print version information and exit.
Assume an answer of `yes' to all questions; allows
to be used non-interactively. This option
may not be specified at the same time as the
- -z undo_file
Before overwriting a file system block, write the old contents of the block to
an undo file. This undo file can be used with e2undo(8) to restore the old
contents of the file system should something go wrong. If the empty string is
passed as the undo_file argument, the undo file will be written to a file named
e2fsck-device.e2undo in the directory specified via the
E2FSPROGS_UNDO_DIR environment variable.
WARNING: The undo file cannot be used to recover from a power or system crash.
The exit code returned by
is the sum of the following conditions:
0 - No errors
1 - File system errors corrected
2 - File system errors corrected, system should
4 - File system errors left uncorrected
8 - Operational error
16 - Usage or syntax error
32 - E2fsck canceled by user request
128 - Shared library error
The following signals have the following effect when sent to
This signal causes
to start displaying a completion bar or emitting progress information.
(See discussion of the
This signal causes
to stop displaying a completion bar or emitting progress information.
Almost any piece of software will have bugs. If you manage to find a
filesystem which causes
to crash, or which
is unable to repair, please report it to the author.
Please include as much information as possible in your bug report.
Ideally, include a complete transcript of the
run, so I can see exactly what error messages are displayed. (Make sure
the messages printed by
are in English; if your system has been
configured so that
messages have been translated into another language, please set the the
environment variable to
so that the transcript of e2fsck's output will be useful to me.)
have a writable filesystem where the transcript can be stored, the
program is a handy way to save the output of
to a file.
It is also useful to send the output of
If a specific inode or inodes seems to be giving
trouble, try running the
command and send the output of the
command run on the relevant inode(s). If the inode is a directory, the
command will allow you to extract the contents of the directory inode,
which can sent to me after being first run through
The most useful data you can send to help reproduce
the bug is a compressed raw image dump of the filesystem, generated using
man page for more details.
Always include the full version string which
displays when it is run, so I know which version you are running.
Determines the location of the configuration file (see
This version of
was written by Theodore Ts'o <email@example.com