Section: System Administration (8)
Updated: July 1996Index
Return to Main Contents
fsck.minix - check consistency of Minix filesystem
performs a consistency check for the Linux MINIX filesystem. The current
version supports the 14 character and 30 character filename options.
assumes the filesystem is quiescent.
should not be used on a mounted device unless you can be sure nobody is
writing to it (and remember that the kernel can write to it when it
searches for files).
The device name will usually have the following form:
- /dev/hda[1-63] (IDE disk 1)
/dev/hdb[1-63] (IDE disk 2)
/dev/sda[1-15] (SCSI disk 1)
/dev/sdb[1-15] (SCSI disk 2)
If the filesystem was changed (i.e., repaired), then
will print "FILE SYSTEM HAS CHANGED" and will
three times before exiting. Since Linux does not currently have raw
devices, there is
need to reboot at this time.
be used on a mounted filesystem. Using
on a mounted filesystem is very dangerous, due to the possibility that
deleted files are still in use, and can seriously damage a perfectly good
filesystem! If you absolutely have to run
on a mounted filesystem (i.e., the root filesystem), make sure nothing is
writing to the disk, and that no files are "zombies" waiting for deletion.
List all filenames.
Perform interactive repairs.
Perform automatic repairs. (This option implies
and serves to answer all of the questions asked with the default.) Note
that this can be extremely dangerous in the case of extensive filesystem
Output super-block information.
Activate MINIX-like "mode not cleared" warnings.
Force a filesystem check even if the filesystem was marked as valid (this
marking is done by the kernel when the filesystem is unmounted).
There are numerous diagnostic messages. The ones mentioned here are the
most commonly seen in normal usage.
If the device does not exist,
will print "unable to read super block". If the device exists, but is not
a MINIX filesystem,
will print "bad magic number in super-block".
The exit code returned by
is the sum of the following:
Filesystem errors corrected, system should be rebooted if filesystem was
Filesystem errors left uncorrected
Combination of exit codes 3 and 4
Usage or syntax error
In point of fact, only 0, 3, 4, 7, 8, and 16 can ever be returned.
Linus Torvalds (firstname.lastname@example.org
Error code values by Rik Faith (email@example.com
Added support for filesystem valid flag: Dr. Wettstein
Check to prevent fsck of mounted filesystem added by Daniel Quinlan
Minix v2 fs support by Andreas Schwab
), updated by Nicolai
Portability patch by Russell King (firstname.lastname@example.org
The fsck.minix command is part of the util-linux package and is available from
- SEE ALSO
- EXIT CODES