{"id":3839,"date":"2022-12-20T17:20:13","date_gmt":"2022-12-20T20:20:13","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/e2fsck-man8-4\/"},"modified":"2022-12-20T17:20:13","modified_gmt":"2022-12-20T20:20:13","slug":"e2fsck-man8-4","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/e2fsck-man8-4\/","title":{"rendered":"E2FSCK (man8)"},"content":{"rendered":"

E2FSCK<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
EXIT CODE<\/a>
SIGNALS<\/a>
REPORTING BUGS<\/a>
ENVIRONMENT<\/a>
AUTHOR<\/a>
SEE ALSO<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

e2fsck \u2212 check a Linux ext2\/ext3\/ext4 file system<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

e2fsck<\/b> [ \u2212pacnyrdfkvtDFV<\/b> ] [ \u2212b<\/b> superblock<\/i> ] [ \u2212B<\/b> blocksize<\/i> ] [ \u2212l<\/b>|\u2212L<\/b> bad_blocks_file<\/i> ] [ \u2212C<\/b> fd<\/i> ] [ \u2212j<\/b> external-journal<\/i> ] [ \u2212E<\/b> extended_options<\/i> ] [ \u2212z<\/b> undo_file<\/i> ] device<\/i><\/p>\n

DESCRIPTION <\/a> <\/h2>\n

e2fsck<\/b><\/i> 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, e2fsck<\/b> will normally replay the journal and exit, unless its superblock indicates that further checking is required.<\/p>\n

device<\/i> is a block device (e.g., \/dev\/sdc1<\/i>) or file containing the file system.<\/p>\n

Note that in general it is not safe to run e2fsck<\/b> on mounted filesystems. The only exception is if the \u2212n<\/b> option is specified, and \u2212c<\/b>, \u2212l<\/b>, or -L<\/b> options are not<\/i> specified. However, even if it is safe to do so, the results printed by e2fsck<\/b> are not valid if the filesystem is mounted. If e2fsck<\/b> asks whether or not you should check a filesystem which is mounted, the only correct answer is \u2018\u2018no\u2019\u2019. Only experts who really know what they are doing should consider answering this question in any other way.<\/p>\n

If e2fsck<\/b> is run in interactive mode (meaning that none of \u2212y<\/b>, \u2212n<\/b>, or \u2212p<\/b> are specified), the program will ask the user to fix each problem found in the filesystem. A response of \u2019y\u2019 will fix the error; \u2019n\u2019 will leave the error unfixed; and \u2019a\u2019 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.<\/p>\n

OPTIONS <\/a> <\/h2>\n\n\n
<\/td>\n\n

\u2212a<\/b><\/p>\n<\/td>\n

<\/td>\n\n

This option does the same thing as the \u2212p<\/b> option. It is provided for backwards compatibility only; it is suggested that people use \u2212p<\/b> option whenever possible.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212b<\/b> superblock<\/i><\/p>\n

Instead of using the normal superblock, use an alternative superblock specified by superblock<\/i>. This option is normally used when the primary superblock has been corrupted. The location of backup superblocks is dependent on the filesystem\u2019s blocksize, the number of blocks per group, and features such as sparse_super<\/b>.<\/p>\n

Additional backup superblocks can be determined by using the mke2fs<\/b> program using the \u2212n<\/b> option to print out where the superblocks exist, supposing mke2fs<\/b> is supplied with arguments that are consistent with the filesystem\u2019s layout (e.g. blocksize, blocks per group, sparse_super<\/b>, etc.).<\/p>\n

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 filesystem check.<\/p>\n

\u2212B<\/b> blocksize<\/i><\/p>\n

Normally, e2fsck<\/b> 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 e2fsck<\/b> to only try locating the superblock at a particular blocksize. If the superblock is not found, e2fsck<\/b> will terminate with a fatal error.<\/p>\n\n\n\n\n\n
<\/td>\n\n

\u2212c<\/b><\/p>\n<\/td>\n

<\/td>\n\n

This option causes e2fsck<\/b> to use badblocks<\/b>(8) 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.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212C<\/b> fd<\/i><\/p>\n<\/td>\n

<\/td>\n\n

This option causes e2fsck<\/b> 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 e2fsck<\/b>. 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 e2fsck<\/b> process a SIGUSR1 signal. If the file descriptor specified is 0, e2fsck<\/b> will print a completion bar as it goes about its business. This requires that e2fsck is running on a video console or terminal.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212d<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Print debugging output (useless unless you are debugging e2fsck<\/b>).<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212D<\/b><\/p>\n<\/td>\n

<\/td>\n\n

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.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

Even without the \u2212D<\/b> option, e2fsck<\/b> 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 \u2212D<\/b> 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.<\/p>\n

The \u2212D<\/b> option will detect directory entries with duplicate names in a single directory, which e2fsck normally does not enforce for performance reasons.<\/p>\n

\u2212E<\/b> extended_options<\/i><\/p>\n

Set e2fsck extended options. Extended options are comma separated, and may take an argument using the equals (\u2019=\u2019) sign. The following options are supported:<\/p>\n

ea_ver=<\/b>extended_attribute_version<\/i><\/p>\n

Set the version of the extended attribute blocks which e2fsck<\/b> will require while checking the filesystem. The version number may be 1 or 2. The default extended attribute version format is 2.<\/p>\n

journal_only<\/b><\/p>\n

Only replay the journal if required, but do not perform any further checks or repairs.<\/p>\n

fragcheck<\/b><\/p>\n

During pass 1, print a detailed report of any discontiguous blocks for files in the filesystem.<\/p>\n

discard<\/b><\/p>\n

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 e2fsck<\/b> does not fully recognize a problem and hence in this case this option may prevent you from further manual data recovery.<\/p>\n

nodiscard<\/b><\/p>\n

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.<\/p>\n

no_optimize_extents<\/b><\/p>\n

Do not offer to optimize the extent tree by eliminating unnecessary width or depth. This can also be enabled in the options section of \/etc\/e2fsck.conf<\/b>.<\/p>\n

optimize_extents<\/b><\/p>\n

Offer to optimize the extent tree by eliminating unnecessary width or depth. This is the default unless otherwise specified in \/etc\/e2fsck.conf<\/b>.<\/p>\n

inode_count_fullmap<\/b><\/p>\n

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 \/etc\/e2fsck.conf<\/b>.<\/p>\n

no_inode_count_fullmap<\/b><\/p>\n

Disable the inode_count_fullmap<\/b> optimization. This is the default unless otherwise specified in \/etc\/e2fsck.conf<\/b>.<\/p>\n

readahead_kb<\/b><\/p>\n

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\u2019 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.<\/p>\n

bmap2extent<\/b><\/p>\n

Convert block-mapped files to extent-mapped files.<\/p>\n

fixes_only<\/b><\/p>\n

Only fix damaged metadata; do not optimize htree directories or compress extent trees. This option is incompatible with the -D and -E bmap2extent options.<\/p>\n

unshare_blocks<\/b><\/p>\n

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.<\/p>\n

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 be non-zero.<\/p>\n\n\n\n
<\/td>\n\n

\u2212f<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Force checking even if the file system seems clean.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212F<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Flush the filesystem device\u2019s buffer caches before beginning. Only really useful for doing e2fsck<\/b> time trials.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212j<\/b> external-journal<\/i><\/p>\n

Set the pathname where the external-journal for this filesystem can be found.<\/p>\n\n\n
<\/td>\n\n

\u2212k<\/b><\/p>\n<\/td>\n

<\/td>\n\n

When combined with the \u2212c<\/b> option, any existing bad blocks in the bad blocks list are preserved, and any new bad blocks found by running badblocks<\/b>(8) will be added to the existing bad blocks list.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212l<\/b> filename<\/i><\/p>\n

Add the block numbers listed in the file specified by filename<\/i> to the list of bad blocks. The format of this file is the same as the one generated by the badblocks<\/b>(8) program. Note that the block numbers are based on the blocksize of the filesystem. Hence, badblocks<\/b>(8) 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 -c<\/b> option to e2fsck<\/b>, since it will assure that the correct parameters are passed to the badblocks<\/b> program.<\/p>\n

\u2212L<\/b> filename<\/i><\/p>\n

Set the bad blocks list to be the list of blocks specified by filename<\/i>. (This option is the same as the \u2212l<\/b> option, except the bad blocks list is cleared before the blocks listed in the file are added to the bad blocks list.)<\/p>\n\n\n\n\n\n\n\n\n
<\/td>\n\n

\u2212n<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Open the filesystem read-only, and assume an answer of \u2018no\u2019 to all questions. Allows e2fsck<\/b> to be used non-interactively. This option may not be specified at the same time as the \u2212p<\/b> or \u2212y<\/b> options.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212p<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Automatically repair (“preen”) the file system. This option will cause e2fsck<\/b> to automatically fix any filesystem problems that can be safely fixed without human intervention. If e2fsck<\/b> discovers a problem which may require the system administrator to take additional corrective action, e2fsck<\/b> will print a description of the problem and then exit with the value 4 logically or\u2019ed into the exit code. (See the EXIT CODE<\/b> section.) This option is normally used by the system\u2019s boot scripts. It may not be specified at the same time as the \u2212n<\/b> or \u2212y<\/b> options.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212r<\/b><\/p>\n<\/td>\n

<\/td>\n\n

This option does nothing at all; it is provided only for backwards compatibility.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212t<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Print timing statistics for e2fsck<\/b>. If this option is used twice, additional timing statistics are printed on a pass by pass basis.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212v<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Verbose mode.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212V<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Print version information and exit.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212y<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Assume an answer of \u2018yes\u2019 to all questions; allows e2fsck<\/b> to be used non-interactively. This option may not be specified at the same time as the \u2212n<\/b> or \u2212p<\/b> options.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212z<\/b> undo_file<\/i><\/p>\n

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<\/i>.e2undo in the directory specified via the E2FSPROGS_UNDO_DIR<\/i> environment variable.<\/p>\n

WARNING: The undo file cannot be used to recover from a power or system crash.<\/p>\n

EXIT CODE <\/a> <\/h2>\n

The exit code returned by e2fsck<\/b> is the sum of the following conditions:
0 \u2212\u00a0No errors
1 \u2212\u00a0File system errors corrected
2 \u2212\u00a0File system errors corrected, system should
\u00a0\u00a0be rebooted
4 \u2212\u00a0File system errors left uncorrected
8 \u2212\u00a0Operational error
16 \u2212\u00a0Usage or syntax error
32 \u2212\u00a0E2fsck canceled by user request
128 \u2212\u00a0Shared library error<\/p>\n

SIGNALS <\/a> <\/h2>\n

The following signals have the following effect when sent to e2fsck<\/b>.
SIGUSR1<\/b><\/p>\n

This signal causes e2fsck<\/b> to start displaying a completion bar or emitting progress information. (See discussion of the \u2212C<\/b> option.)<\/p>\n

SIGUSR2<\/b><\/p>\n

This signal causes e2fsck<\/b> to stop displaying a completion bar or emitting progress information.<\/p>\n

REPORTING BUGS <\/a> <\/h2>\n

Almost any piece of software will have bugs. If you manage to find a filesystem which causes e2fsck<\/b> to crash, or which e2fsck<\/b> is unable to repair, please report it to the author.<\/p>\n

Please include as much information as possible in your bug report. Ideally, include a complete transcript of the e2fsck<\/b> run, so I can see exactly what error messages are displayed. (Make sure the messages printed by e2fsck<\/b> are in English; if your system has been configured so that e2fsck<\/b>\u2019s messages have been translated into another language, please set the the LC_ALL<\/b> environment variable to C<\/b> so that the transcript of e2fsck\u2019s output will be useful to me.) If you have a writable filesystem where the transcript can be stored, the script<\/b>(1) program is a handy way to save the output of e2fsck<\/b> to a file.<\/p>\n

It is also useful to send the output of dumpe2fs<\/b>(8). If a specific inode or inodes seems to be giving e2fsck<\/b> trouble, try running the debugfs<\/b>(8) command and send the output of the stat<\/b>(1u) command run on the relevant inode(s). If the inode is a directory, the debugfs<\/b> dump<\/i> command will allow you to extract the contents of the directory inode, which can sent to me after being first run through uuencode<\/b>(1). The most useful data you can send to help reproduce the bug is a compressed raw image dump of the filesystem, generated using e2image<\/b>(8). See the e2image<\/b>(8) man page for more details.<\/p>\n

Always include the full version string which e2fsck<\/b> displays when it is run, so I know which version you are running.<\/p>\n

ENVIRONMENT <\/a> <\/h2>\n

E2FSCK_CONFIG<\/b><\/p>\n

Determines the location of the configuration file (see e2fsck.conf<\/b>(5)).<\/p>\n

AUTHOR <\/a> <\/h2>\n

This version of e2fsck<\/b> was written by Theodore Ts\u2019o .<\/p>\n

SEE ALSO <\/a> <\/h2>\n

e2fsck.conf<\/b>(5), badblocks<\/b>(8), dumpe2fs<\/b>(8), debugfs<\/b>(8), e2image<\/b>(8), mke2fs<\/b>(8), tune2fs<\/b>(8)<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

e2fsck \u2212 check a Linux ext2\/ext3\/ext4 file system <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,31,4],"class_list":["post-3839","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-fsck","tag-man8"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3839","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3839"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3839\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3839"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3839"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3839"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}