check consistency of Minix filesystem
see also :
fsck - fsck.ext2 - mkfs - mkfs.minix - mkfs.ext2 - reboot
add an example, a script, a trick and tips
find findfs fold free freeramdisk fsck
fsck.minix fsync ftpd ftpget ftpput
fuser getopt getty grep gunzip gzip halt hd
hdparm head hexdump hostid
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. fsck.minix
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).
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)
filesystem was changed (i.e., repaired), then
fsck.minix will print "FILE SYSTEM HAS
CHANGED" and will sync(2) three times before
exiting. Since Linux does not currently have raw devices,
there is no need to reboot at this time.
List all filenames.
Perform interactive repairs.
Perform automatic repairs. (This option implies
-r 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.
Output super-block information.
Activate MINIX-like "mode not cleared"
Force a filesystem check even if the filesystem was
marked as valid (this marking is done by the kernel when the
filesystem is unmounted).
The fsck.minix command is part of the util-linux package and is
available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
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, fsck.minix will print "bad magic number
The exit code returned by fsck.minix is the sum of the
Filesystem errors corrected, system should be rebooted if
filesystem was mounted
Filesystem errors left uncorrected
Usage or syntax error
In point of fact, only 0, 3, 4, 7, 8, and 16 can ever be
fsck.minix should not be used on a mounted
filesystem. Using fsck.minix 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 on a
mounted filesystem (i.e., the root filesystem), make sure nothing
is writing to the disk, and that no files are "zombies" waiting
fsck.ext, fsck.ext2 ,
fsck.xiafs, mkfs , mkfs.minix ,
mkfs.ext, mkfs.ext2 ,
Error code values by Rik Faith (faith[:at:]cs.unc[:dot:]edu)
Added support for filesystem valid flag: Dr. Wettstein
Check to prevent fsck of mounted filesystem added by Daniel
Minix v2 fs support by Andreas Schwab
(schwab[:at:]issan.informatik[:dot:]uni-dortmund.de), updated by
Nicolai Langfeldt (janl[:at:]math.uio[:dot:]no)
Portability patch by Russell King (rmk[:at:]ecs.soton.ac[:dot:]uk).