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
36
is used to check a Linux second extended file system (e2fs). E2fsck also
37
supports ext2 filesystems countaining a journal, which are
38
also sometimes known as ext3 filesystems.
41
is the device file where the filesystem is stored (e.g.
46
This option does the same thing as the
48
option. It is provided for backwards compatibility only; it is
49
suggested that people use
51
option whenever possible.
54
Instead of using the normal superblock, use an alternative superblock
57
This option is normally used when the primary superblock has been
58
corrupted. The location of the backup superblock is dependent on the
59
filesystem's blocksize. For filesystems with 1k blocksizes, a backup
60
superblock can be found at block 8193; for filesystems with 2k
61
blocksizes, at block 16384; and for 4k blocksizes, at block 32768.
63
Additional backup superblocks can be determined by using the
67
option to print out where the superblocks were created. The
71
which specifies blocksize of the filesystem must be specified in order
72
for the superblock locations that are printed out to be accurate.
74
If an alternative superblock is specified and
75
the filesystem is not opened read-only, e2fsck will make sure that the
76
primary superblock is updated appropriately upon completion of the
82
will search for the superblock at various different
83
block sizes in an attempt to find the appropriate block size.
84
This search can be fooled in some cases. This option forces
86
to only try locating the superblock at a particular blocksize.
87
If the superblock is not found,
89
will terminate with a fatal error.
96
program to find any blocks which are bad on the filesystem,
97
and then marks them as bad by adding them to the bad block inode.
98
If this option is specified twice, then the bad block scan will be done
99
using a non-destructive read-write test.
104
to write completion information to the specified file descriptor
105
so that the progress of the filesystem
106
check can be monitored. This option is typically used by programs
109
If the file descriptor specified is 0,
111
will print a completion bar as it goes about its business. This requires
112
that e2fsck is running on a video console or terminal.
115
Print debugging output (useless unless you are debugging
119
Force checking even if the file system seems clean.
122
Flush the filesystem device's buffer caches before beginning. Only
123
really useful for doing
127
@JDEV@.BI \-j " external-journal"
128
@JDEV@Set the pathname where the external-journal for this filesystem can be
132
Add the block numbers listed in the file specified by
134
to the list of bad blocks. The format of this file is the same as the
137
program. Note that the block numbers are based on the blocksize
138
of the filesystem. Hence,
140
must be given the blocksize of the filesystem in order to obtain correct
141
results. As a result, it is much simpler and safer to use the
145
since it will assure that the correct parameters are passed to the
150
Set the bad blocks list to be the list of blocks specified by
152
(This option is the same as the
154
option, except the bad blocks list is cleared before the blocks listed
155
in the file are added to the bad blocks list.)
158
Open the filesystem read-only, and assume an answer of `no' to all
161
to be used non-interactively. (Note: if the
166
options are specified in addition to the
168
option, then the filesystem will be opened read-write, to permit the
169
bad-blocks list to be updated. However, no other changes will be made
173
Automatically repair ("preen") the file system without any questions.
176
This option does nothing at all; it is provided only for backwards
180
This option will byte-swap the filesystem so that it is using the normalized,
181
standard byte-order (which is i386 or little endian). If the filesystem is
182
already in the standard byte-order,
187
This option will byte-swap the filesystem, regardless of its current
191
Print timing statistics for
193
If this option is used twice, additional timing statistics are printed
194
on a pass by pass basis.
200
Print version information and exit.
203
Assume an answer of `yes' to all questions; allows
205
to be used non-interactively.
207
The exit code returned by
209
is the sum of the following conditions:
213
\ 1\ \-\ File system errors corrected
215
\ 2\ \-\ File system errors corrected, system should
217
\ \ \ \ be rebooted if file system was mounted
219
\ 4\ \-\ File system errors left uncorrected
221
\ 8\ \-\ Operational error
223
\ 16\ \-\ Usage or syntax error
225
\ 128\ \-\ Shared library error
228
The following signals have the following effect when sent to
234
to start displaying a completion bar. (See discussion of the
241
to stop displaying a completion bar.
243
Almost any piece of software will have bugs. If you manage to find a
244
filesystem which causes
248
is unable to repair, please report it to the author.
250
Please include as much information as possible in your bug report.
251
Ideally, include a complete transcript of the
253
run, so I can see exactly what error messages are displayed. If you
254
have a writeable filesystem where the transcript can be stored, the
256
program is a handy way to save the output of
260
It is also useful to send the output of
262
If a specific inode or inodes seems to be giving
264
trouble, try running the
266
command and send the output of the
268
command run on the relevant inode(s). If the inode is a directory, the
271
command will allow you to extract the contents of the directory inode,
272
which can sent to me after being first run through
275
Always include the full version string which
277
displays when it is run, so I know which version you are running.
281
was written by Theodore Ts'o <tytso@mit.edu>.
added
removed
e2fsck/e2fsck.8.in
