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. The location of the backup superblock is dependent on the
53 filesystem's blocksize. For filesystems with 1k blocksizes, a backup
54 superblock can be found at block 8193; for filesystems with 2k
55 blocksizes, at block 16384; and for 4k blocksizes, at block 32768. If
56 an alternative superblock is specified and
57 the filesystem is not opened read-only, e2fsck will make sure that the
58 primary superblock is updated appropriately upon completion of the
64 will search for the superblock at various different
65 block sizes in an attempt to find the appropriate block size.
66 This search can be fooled in some cases. This option forces
68 to only try locating the superblock at a particular blocksize.
69 If the superblock is not found,
71 will terminate with a fatal error.
78 program to find any blocks which are bad on the filesystem,
79 and then marks them as bad by adding them to the bad block inode.
84 to write completion information to the specified file descriptor
85 so that the progress of the filesystem
86 check can be monitored. This option is typically used by programs
89 If the file descriptor specified is 0,
91 will print a completion bar as it goes about its business. This requires
92 that e2fsck is running on a video console or terminal.
95 Print debugging output (useless unless you are debugging
99 Force checking even if the file system seems clean.
102 Flush the filesystem device's buffer caches before beginning. Only
103 really useful for doing
108 Add the blocks listed in the file specified by
110 to the list of bad blocks. The format of this file is the same as the
116 Set the bad blocks list to be the list of blocks specified by
118 (This option is the same as the
120 option, except the bad blocks list is cleared before the blocks listed
121 in the file are added to the bad blocks list.)
124 Open the filesystem read-only, and assume an answer of `no' to all
127 to be used non-interactively. (Note: if the
132 options are specified in addition to the
134 option, then the filesystem will be opened read-write, to permit the
135 bad-blocks list to be updated. However, no other changes will be made
139 Automatically repair ("preen") the file system without any questions.
142 This option does nothing at all; it is provided only for backwards
146 This option will byte-swap the filesystem so that it is using the normalized,
147 standard byte-order (which is i386 or little endian). If the filesystem is
148 already in the standard byte-order,
153 This option will byte-swap the filesystem, regardless of its current
157 Print timing statistics for
159 If this option is used twice, additional timing statistics are printed
160 on a pass by pass basis.
166 Print version information and exit.
169 Assume an answer of `yes' to all questions; allows
171 to be used non-interactively.
173 The exit code returned by
175 is the sum of the following conditions:
179 \ 1\ \-\ File system errors corrected
181 \ 2\ \-\ File system errors corrected, system should
183 \ \ \ \ be rebooted if file system was mounted
185 \ 4\ \-\ File system errors left uncorrected
187 \ 8\ \-\ Operational error
189 \ 16\ \-\ Usage or syntax error
191 \ 128\ \-\ Shared library error
194 The following signals have the following effect when sent to
200 to start displaying a completion bar. (See discussion of the
207 to stop displaying a completion bar.
209 Almost any piece of software will have bugs. If you manage to find a
210 filesystem which causes
214 is unable to repair, please report it to the author.
216 Please include as much information as possible in your bug report.
217 Ideally, include a complete transcript of the
219 run, so I can see exactly what error messages are displayed. If you
220 have a writeable filesystem where the transcript can be stored, the
222 program is a handy way to save the output of
226 It is also useful to send the output of
228 If a specific inode or inodes seems to be giving
230 trouble, try running the
232 command and send the output of the
234 command run on the relevant inode(s). If the inode is a directory, the
237 command will allow you to extract the contents of the directory inode,
238 which can sent to me after being first run through
241 Always include the full version string which
243 displays when it is run, so I know which version you are running.
247 was written by Theodore Ts'o <tytso@mit.edu>.