fsck.minix - check consistency of Minix filesystem
performs a consistency check for the Linux MINIX filesystem.
The program assumes the filesystem is quiescent. fsck.minix
should not be
used on a mounted device unless you can be sure nobody is writing to it.
Remember that the kernel can write to device when it searches for files.
name will usually have the following form:
||IDE disk 1
||IDE disk 2
||SCSI disk 1
||SCSI disk 2
If the filesystem was changed, i.e., repaired, then fsck.minix
"FILE SYSTEM HAS CHANGED" and will sync(2)
three times before
exiting. There is no
need to reboot after check.
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 fsck.minix
a mounted filesystem, such as the root filesystem, make sure nothing is
writing to the disk, and that no files are "zombies" waiting for
- -l, --list
- List all filenames.
- -r, --repair
- Perform interactive repairs.
- -a, --auto
- Perform automatic repairs. This option implies
--repair 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 damage.
- -v, --verbose
- Be verbose.
- -s, --super
- Output super-block information.
- -m, --uncleared
- Activate MINIX-like "mode not cleared"
- -f, --force
- Force a filesystem check even if the filesystem was marked
as valid. Marking is done by the kernel when the filesystem is
- -V, --version
- Display version information and exit.
- -h, --help
- Display help text and exit.
There are numerous diagnostic messages. The ones mentioned here are the most
commonly seen in normal usage.
If the device does not exist, fsck.minix
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 fsck.minix
is the sum of the following:
- No errors
- Filesystem errors corrected, system should be rebooted if
filesystem was mounted
- Filesystem errors left uncorrected
- Combination of exit codes 3 and 4
- Operational error
- Usage or syntax error
Error code values by Rik
Added support for filesystem valid flag:
Check to prevent fsck of mounted filesystem added by
Minix v2 fs support by
Portability patch by
The fsck.minix command is part of the util-linux package and is available from