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 FSCK 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
7 fsck \- check and repair a Linux file system
26 is used to check and optionally repair a Linux file system.
28 is either the device name (e.g. /dev/hda1, /dev/sdb2) or the mount point
29 (e.g. /, /usr, /home) for the file system. If this fsck has several
30 filesystems on different physical disk drives to check, this fsck will
31 try to run them in parallel. This reduces the total amount time it
32 takes to check all of the filesystems, since fsck takes advantage of the
33 parallelism of multiple disk spindles.
35 The exit code returned by
37 is the sum of the following conditions:
41 \ 1\ \-\ File system errors corrected
43 \ 2\ \-\ System should be rebooted
45 \ 4\ \-\ File system errors left uncorrected
47 \ 8\ \-\ Operational error
49 \ 16\ \-\ Usage or syntax error
51 \ 128\ \-\ Shared library error
53 The exit code returned when all file systems are checked using the
55 option is the bit-wise OR of the exit codes for each
56 file system that is checked.
60 is simply a front-end for the various file system checkers
61 (\fBfsck\fR.\fIfstype\fR) available under Linux. The file
62 system-specific checker is searched for in /sbin first, then in /etc/fs
63 and /etc, and finally in the directories listed in the PATH environment
64 variable. Please see the file system-specific checker manual pages for
71 file and try to check all file systems in one run. This option is
72 typically used from the
74 system initalization file, instead of multiple commands for checking
78 When checking all file systems with the
80 flag, skip the root file system (in case it's already mounted read-write).
83 Don't show the title on startup.
86 Don't execute, just show what would be done.
89 Serialize fsck operations. This is a good idea if you checking multiple
90 filesystems in and the checkers are in an interactive mode. (Note:
92 runs in an interactive mode by default. To make
94 run in a non-interactive mode, you must either specify the
98 option, if you wish for errors to be corrected automatically, or
101 option if you do not.)
104 Produce verbose output, including all file system-specific commands
108 Specifies the type of file system to be checked. When the
110 flag is specified, only filesystems that match
116 only filesystems whose filesystem do not match
120 Normally, the filesystem type is deduced by searching for
124 file and using the corresponding entry.
125 If the type can not be deduced,
127 will use the type specified by the
129 option if it specifies a unique filesystem type. If this type is not
130 available, the the default file system type
131 (currently ext2) is used.
134 Any options which are not understood by
138 option are treated as file system-specific options to be passed to the
139 file system-specific checker.
141 Currently, standardized file system-specific options are somewhat in
142 flux. Although not guaranteed, the following options are supported
143 by most file system checkers.
146 Automatically repair the file system without any questions (use
147 this option with caution). Note that
151 for backwards compatibility only. This option is mapped to e2fsck's
153 option which is safe to use, unlike the
155 option that most file system checkers support.
158 Interactively repair the filesystem (ask for confirmations). Note: It
159 is generally a bad idea to use this option if multiple fsck's are being
160 run in parallel. Also note that this is
162 default behavior; it supports this option for backwards compatibility
165 Theodore Ts'o (tytso@mit.edu)
167 The manual page was shamelessly adapted from David Engel and Fred van
168 Kempen's generic fsck front end program, which was in turn shamelessly
169 adapted from Remy Card's version for the ext2 file system.