2 .TH FSCK 8 "Mar 1994" "Version 0.5"
4 fsck \- check and repair a Linux file system
23 is used to check and optionally repair a Linux file system.
25 is either the device name (e.g. /dev/hda1, /dev/sdb2) or the mount point
26 (e.g. /, /usr, /home) for the file system. If this fsck has several
27 filesystems on different physical disk drives to check, this fsck will
28 try to run them in parallel. This reduces the total amount time it
29 takes to check all of the filesystems, since fsck takes advantage of the
30 parallelism of multiple disk spindles.
32 The exit code returned by
34 is the sum of the following conditions:
38 \ 1\ \-\ File system errors corrected
40 \ 2\ \-\ System should be rebooted
42 \ 4\ \-\ File system errors left uncorrected
44 \ 8\ \-\ Operational error
46 \ 16\ \-\ Usage or syntax error
48 \ 128\ \-\ Shared library error
50 The exit code returned when all file systems are checked using the
52 option is the bit-wise OR of the exit codes for each
53 file system that is checked.
57 is simply a front-end for the various file system checkers
58 (\fBfsck\fR.\fIfstype\fR) available under Linux. The file
59 system-specific checker is searched for in /sbin first, then in /etc/fs
60 and /etc, and finally in the directories listed in the PATH environment
61 variable. Please see the file system-specific checker manual pages for
68 file and try to check all file systems in one run. This option is
69 typically used from the
71 system initalization file, instead of multiple commands for checking
72 a single file system. Note, that with this option, you cannot give
78 Serialize fsck operations. This is a good idea if you checking multiple
79 filesystems in and the checkers are in an interactive mode. (Note:
81 runs in an interactive mode by default. To make
83 run in a non-interactive mode, you must either specify the
87 option, if you wish for errors to be corrected automatically, or
90 option if you do not.)
93 Produce verbose output, including all file system-specific commands
95 Specifying this option more than once inhibits execution of any
96 file system-specific commands.
97 This is really only useful for testing.
100 Specifies the type of file system to be checked.
101 If not specified, the type is deduced by searching for
105 and using the corresponding entry.
106 If the type can not be deduced, the default file system type
107 (currently ext2) is used.
110 Any options which are not understood by
114 option are treated as file system-specific options to be passed to the
115 realm file system checker.
117 Currently, standardized file system-specific options are somewhat in
118 flux. Although not guaranteed, the following options are supported
119 by most file system checkers.
122 Automatically repair the file system without any questions (use
123 this option with caution). Note that
127 for backwards compatibility only. This option is mapped to e2fsck's
129 option which is safe to use, unlike the
131 option that most file system checkers support.
134 Interactively repair the filesystem (ask for confirmations). Note: It
135 is generally a bad idea to use this option if multiple fsck's are being
136 run in parallel. Also note that this is
138 default behavior; it supports this option for backwards compatibility
141 Theodore Ts'o (tytso@mit.edu)
143 The manual page was shamelessly adapted from David Engel and Fred van
144 Kempen's generic fsck front end program, which was in turn shamelessly
145 adapted from Remy Card's version for the ext2 file system.