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.
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 fsck.minix will print "FILE SYSTEM HAS CHANGED" and will sync(2) three times before exiting. There is no need to reboot after check.
- -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" warnings.
- -f, --force
- Force a filesystem check even if the filesystem was marked as valid. Marking is done by the kernel when the filesystem is unmounted.
- -V, --version
- Display version information and exit.
- -h, --help
- Display help text and exit.
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 in super-block".
- 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 Faith
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 Langfeldt.
Portability patch by Russell King.