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 ext2/ext3 file system
31 @JDEV@.I external-journal
40 is used to check a Linux second extended file system (ext2fs).
43 supports ext2 filesystems containing a journal, which are
44 also sometimes known as ext3 filesystems, by first applying the journal
45 to the filesystem before continuing with normal
47 processing. After the journal has been applied, a filesystem will
48 normally be marked as clean. Hence, for ext3 filesystems,
50 will normally run the journal and exit, unless its superblock
51 indicates that further checking is required.
54 is the device file where the filesystem is stored (e.g.
57 Note that in general it is not safe to run
59 on mounted filesystems. The only exception is if the
61 option is specified, and
68 specified. However, even if it is safe to do so, the results printed by
70 are not valid if the filesystem is mounted. If
72 asks whether or not you should check a filesystem which is mounted,
73 the only correct answer is ``no''. Only experts who really know what
74 they are doing should consider answering this question in any other way.
78 This option does the same thing as the
80 option. It is provided for backwards compatibility only; it is
81 suggested that people use
83 option whenever possible.
86 Instead of using the normal superblock, use an alternative superblock
89 This option is normally used when the primary superblock has been
90 corrupted. The location of the backup superblock is dependent on the
91 filesystem's blocksize. For filesystems with 1k blocksizes, a backup
92 superblock can be found at block 8193; for filesystems with 2k
93 blocksizes, at block 16384; and for 4k blocksizes, at block 32768.
95 Additional backup superblocks can be determined by using the
99 option to print out where the superblocks were created. The
103 which specifies blocksize of the filesystem must be specified in order
104 for the superblock locations that are printed out to be accurate.
106 If an alternative superblock is specified and
107 the filesystem is not opened read-only, e2fsck will make sure that the
108 primary superblock is updated appropriately upon completion of the
114 will search for the superblock at various different
115 block sizes in an attempt to find the appropriate block size.
116 This search can be fooled in some cases. This option forces
118 to only try locating the superblock at a particular blocksize.
119 If the superblock is not found,
121 will terminate with a fatal error.
128 program to do a read-only scan of the device in order to find any bad
129 blocks. If any bad blocks are found, they are added to the bad block
130 inode to prevent them from being allocated to a file or directory. If
131 this option is specified twice, then the bad block scan will be done
132 using a non-destructive read-write test.
137 to write completion information to the specified file descriptor
138 so that the progress of the filesystem
139 check can be monitored. This option is typically used by programs
142 If the file descriptor number is negative, then absolute value of
143 the file descriptor will be used, and the progress information will be
144 suppressed initially. It can later be enabled by sending the
146 process a SIGUSR1 signal.
147 If the file descriptor specified is 0,
149 will print a completion bar as it goes about its business. This requires
150 that e2fsck is running on a video console or terminal.
153 Print debugging output (useless unless you are debugging
157 Optimize directories in filesystem. This option causes e2fsck to
158 try to optimize all directories, either by reindexing them if the
159 filesystem supports directory indexing, or by sorting and compressing
160 directories for smaller directories, or for filesystems using
161 traditional linear directories.
167 may sometimes optimize a few directories --- for example, if
168 directory indexing is enabled and a directory is not indexed and would
169 benefit from being indexed, or if the index structures are corrupted
170 and need to be rebuilt. The
172 option forces all directories in the filesystem to be optimized. This can
173 sometimes make them a little smaller and slightly faster to search, but
174 in practice, you should rarely need to use this option.
178 option will detect directory entries with duplicate names in a single
179 directory, which e2fsck normally does not enforce for performance reasons.
181 .BI \-E " extended_options"
182 Set e2fsck extended options. Extended options are comma
183 separated, and may take an argument using the equals ('=') sign. The
184 following options are supported:
187 .BI ea_ver= extended_attribute_version
188 Assume the format of the extended attribute blocks in the filesystem is
189 the specified version number. The version number may be 1 or 2. The
190 default extended attribute version format is 2.
194 Force checking even if the file system seems clean.
197 Flush the filesystem device's buffer caches before beginning. Only
198 really useful for doing
202 @JDEV@.BI \-j " external-journal"
203 @JDEV@Set the pathname where the external-journal for this filesystem can be
207 When combined with the
209 option, any existing bad blocks in the bad blocks list are preserved,
210 and any new bad blocks found by running
212 will be added to the existing bad blocks list.
215 Add the block numbers listed in the file specified by
217 to the list of bad blocks. The format of this file is the same as the
220 program. Note that the block numbers are based on the blocksize
221 of the filesystem. Hence,
223 must be given the blocksize of the filesystem in order to obtain correct
224 results. As a result, it is much simpler and safer to use the
228 since it will assure that the correct parameters are passed to the
233 Set the bad blocks list to be the list of blocks specified by
235 (This option is the same as the
237 option, except the bad blocks list is cleared before the blocks listed
238 in the file are added to the bad blocks list.)
241 Open the filesystem read-only, and assume an answer of `no' to all
244 to be used non-interactively. (Note: if the
249 options are specified in addition to the
251 option, then the filesystem will be opened read-write, to permit the
252 bad-blocks list to be updated. However, no other changes will be made
253 to the filesystem.) This option
254 may not be specified at the same time as the
261 Automatically repair ("preen") the file system. This option will case
264 fix any filesystem problems that can be safely fixed without human
267 discovers a problem which may require the system administrator
268 to take additional corrective action,
270 will print a description of the problem and then exit with the value 4
271 logically or'ed into the exit code. (See the \fBEXIT CODE\fR section.)
272 This option is normally used by the system's boot scripts. It may not
273 be specified at the same time as the
280 This option does nothing at all; it is provided only for backwards
284 Print timing statistics for
286 If this option is used twice, additional timing statistics are printed
287 on a pass by pass basis.
293 Print version information and exit.
296 Assume an answer of `yes' to all questions; allows
298 to be used non-interactively. This option
299 may not be specified at the same time as the
305 The exit code returned by
307 is the sum of the following conditions:
311 \ 1\ \-\ File system errors corrected
313 \ 2\ \-\ File system errors corrected, system should
317 \ 4\ \-\ File system errors left uncorrected
319 \ 8\ \-\ Operational error
321 \ 16\ \-\ Usage or syntax error
323 \ 32\ \-\ E2fsck canceled by user request
325 \ 128\ \-\ Shared library error
328 The following signals have the following effect when sent to
334 to start displaying a completion bar or emitting progress information.
335 (See discussion of the
342 to stop displaying a completion bar or emitting progress information.
344 Almost any piece of software will have bugs. If you manage to find a
345 filesystem which causes
349 is unable to repair, please report it to the author.
351 Please include as much information as possible in your bug report.
352 Ideally, include a complete transcript of the
354 run, so I can see exactly what error messages are displayed. (Make sure
355 the messages printed by
357 are in English; if your system has been
360 messages have been translated into another language, please set the the
362 environment variable to
364 so that the transcript of e2fsck's output will be useful to me.)
366 have a writable filesystem where the transcript can be stored, the
368 program is a handy way to save the output of
372 It is also useful to send the output of
374 If a specific inode or inodes seems to be giving
376 trouble, try running the
378 command and send the output of the
380 command run on the relevant inode(s). If the inode is a directory, the
383 command will allow you to extract the contents of the directory inode,
384 which can sent to me after being first run through
386 The most useful data you can send to help reproduce
387 the bug is a compressed raw image dump of the filesystem, generated using
391 man page for more details.
393 Always include the full version string which
395 displays when it is run, so I know which version you are running.
399 was written by Theodore Ts'o <tytso@mit.edu>.
git://git.whamcloud.com / tools / e2fsprogs.git / blob