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
32 is used to check a Linux second extended file system.
35 is the special file corresponding to the device (e.g
40 This option does the same thing as the
42 option. It is provided for backwards compatibility only; it is
43 suggested that people use
45 option whenever possible.
48 Instead of using the normal superblock, use an alternative superblock
51 This option is normally used when the primary superblock has been
52 corrupted; most filesystems have primary superblocks located at
53 blocks 8193, 16385, etc. If an alternative superblock is specified and
54 the filesystem is not opened read-only, e2fsck will make sure that the
55 primary superblock is updated appropriately upon completion of the
61 will search for the superblock at various different
62 block sizes in an attempt to find the appropriate block size.
63 This search can be fooled in some cases. This option forces
65 to only try locating the superblock at a particular blocksize.
66 If the superblock is not found,
68 will terminate with a fatal error.
75 program to find any blocks which are bad on the filesystem,
76 and then marks them as bad by adding them to the bad block inode.
81 to write completion information to the specified file descriptor
82 so that the progress of the filesystem
83 check can be monitored. This option is typically used by programs
86 If the file descriptor specified is 0,
88 will print a completion bar as it goes about its business. This requires
89 that e2fsck is running on a video console or terminal.
92 Print debugging output (useless unless you are debugging
96 Force checking even if the file system seems clean.
99 Flush the filesystem device's buffer caches before beginning. Only
100 really useful for doing
105 Add the blocks listed in the file specified by
107 to the list of bad blocks. The format of this file is the same as the
113 Set the bad blocks list to be the list of blocks specified by
115 (This option is the same as the
117 option, except the bad blocks list is cleared before the blocks listed
118 in the file are added to the bad blocks list.)
121 Open the filesystem read-only, and assume an answer of `no' to all
124 to be used non-interactively. (Note: if the
129 options are specified in addition to the
131 option, then the filesystem will be opened read-write, to permit the
132 bad-blocks list to be updated. However, no other changes will be made
136 Automatically repair ("preen") the file system without any questions.
139 This option does nothing at all; it is provided only for backwards
143 This option will byte-swap the filesystem so that it is using the normalized,
144 standard byte-order (which is i386 or little endian). If the filesystem is
145 already in the standard byte-order,
150 This option will byte-swap the filesystem, regardless of its current
154 Print timing statistics for
156 If this option is used twice, additional timing statistics are printed
157 on a pass by pass basis.
163 Print version information and exit.
166 Assume an answer of `yes' to all questions; allows
168 to be used non-interactively.
170 The exit code returned by
172 is the sum of the following conditions:
176 \ 1\ \-\ File system errors corrected
178 \ 2\ \-\ File system errors corrected, system should
180 \ \ \ \ be rebooted if file system was mounted
182 \ 4\ \-\ File system errors left uncorrected
184 \ 8\ \-\ Operational error
186 \ 16\ \-\ Usage or syntax error
188 \ 128\ \-\ Shared library error
191 The following signals have the following effect when sent to
197 to start displaying a completion bar. (See discussion of the
204 to stop displaying a completion bar.
206 Almost any piece of software will have bugs. If you manage to find a
207 filesystem which causes
211 is unable to repair, please report it to the author.
213 Please include as much information as possible in your bug report.
214 Ideally, include a complete transcript of the
216 run, so I can see exactly what error messages are displayed. If you
217 have a writeable filesystem where the transcript can be stored, the
219 program is a handy way to save the output of
223 It is also useful to send the output of
225 If a specific inode or inodes seems to be giving
227 trouble, try running the
229 command and send the output of the
231 command run on the relevant inode(s). If the inode is a directory, the
234 command will allow you to extract the contents of the directory inode,
235 which can sent to me after being first run through
238 Always include the full version string which
240 displays when it is run, so I know which version you are running.
244 was written by Theodore Ts'o <tytso@mit.edu>.