2 .\" Copyright 1993, 1994, 1995 by Theodore Ts'o. All Rights Reserved.
3 .\" This file may be copied under the terms of the GNU Public License.
5 .TH E2FSCK 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
7 e2fsck \- check a Linux second extended file system
31 @JDEV@.I external-journal
37 is used to check a Linux second extended file system (e2fs). E2fsck also
38 supports ext2 filesystems countaining a journal, which are
39 also sometimes known as ext3 filesystems.
42 is the special file corresponding to the device (e.g
47 This option does the same thing as the
49 option. It is provided for backwards compatibility only; it is
50 suggested that people use
52 option whenever possible.
55 Instead of using the normal superblock, use an alternative superblock
58 This option is normally used when the primary superblock has been
59 corrupted. The location of the backup superblock is dependent on the
60 filesystem's blocksize. For filesystems with 1k blocksizes, a backup
61 superblock can be found at block 8193; for filesystems with 2k
62 blocksizes, at block 16384; and for 4k blocksizes, at block 32768.
64 Additional backup superblocks can be determined by using the
68 option to print out where the superblocks were created. The
72 which specifies blocksize of the filesystem must be specified in order
73 for the superblock locations that are printed out to be accurate.
75 If an alternative superblock is specified and
76 the filesystem is not opened read-only, e2fsck will make sure that the
77 primary superblock is updated appropriately upon completion of the
83 will search for the superblock at various different
84 block sizes in an attempt to find the appropriate block size.
85 This search can be fooled in some cases. This option forces
87 to only try locating the superblock at a particular blocksize.
88 If the superblock is not found,
90 will terminate with a fatal error.
97 program to find any blocks which are bad on the filesystem,
98 and then marks them as bad by adding them to the bad block inode.
103 to write completion information to the specified file descriptor
104 so that the progress of the filesystem
105 check can be monitored. This option is typically used by programs
108 If the file descriptor specified is 0,
110 will print a completion bar as it goes about its business. This requires
111 that e2fsck is running on a video console or terminal.
114 Print debugging output (useless unless you are debugging
118 Force checking even if the file system seems clean.
121 Flush the filesystem device's buffer caches before beginning. Only
122 really useful for doing
126 @JDEV@.BI \-j " external-journal"
127 @JDEV@Set the pathname where the external-journal for this filesystem can be
131 Add the blocks listed in the file specified by
133 to the list of bad blocks. The format of this file is the same as the
139 Set the bad blocks list to be the list of blocks specified by
141 (This option is the same as the
143 option, except the bad blocks list is cleared before the blocks listed
144 in the file are added to the bad blocks list.)
147 Open the filesystem read-only, and assume an answer of `no' to all
150 to be used non-interactively. (Note: if the
155 options are specified in addition to the
157 option, then the filesystem will be opened read-write, to permit the
158 bad-blocks list to be updated. However, no other changes will be made
162 Automatically repair ("preen") the file system without any questions.
165 This option does nothing at all; it is provided only for backwards
169 This option will byte-swap the filesystem so that it is using the normalized,
170 standard byte-order (which is i386 or little endian). If the filesystem is
171 already in the standard byte-order,
176 This option will byte-swap the filesystem, regardless of its current
180 Print timing statistics for
182 If this option is used twice, additional timing statistics are printed
183 on a pass by pass basis.
189 Print version information and exit.
192 Assume an answer of `yes' to all questions; allows
194 to be used non-interactively.
196 The exit code returned by
198 is the sum of the following conditions:
202 \ 1\ \-\ File system errors corrected
204 \ 2\ \-\ File system errors corrected, system should
206 \ \ \ \ be rebooted if file system was mounted
208 \ 4\ \-\ File system errors left uncorrected
210 \ 8\ \-\ Operational error
212 \ 16\ \-\ Usage or syntax error
214 \ 128\ \-\ Shared library error
217 The following signals have the following effect when sent to
223 to start displaying a completion bar. (See discussion of the
230 to stop displaying a completion bar.
232 Almost any piece of software will have bugs. If you manage to find a
233 filesystem which causes
237 is unable to repair, please report it to the author.
239 Please include as much information as possible in your bug report.
240 Ideally, include a complete transcript of the
242 run, so I can see exactly what error messages are displayed. If you
243 have a writeable filesystem where the transcript can be stored, the
245 program is a handy way to save the output of
249 It is also useful to send the output of
251 If a specific inode or inodes seems to be giving
253 trouble, try running the
255 command and send the output of the
257 command run on the relevant inode(s). If the inode is a directory, the
260 command will allow you to extract the contents of the directory inode,
261 which can sent to me after being first run through
264 Always include the full version string which
266 displays when it is run, so I know which version you are running.
270 was written by Theodore Ts'o <tytso@mit.edu>.