1 //po4a: entry man manual
3 Copyright 1992, 1993, 1994 Rickard E. Faith (faith@cs.unc.edu)
4 May be freely distributed.
8 :man manual: System Administration
9 :man source: util-linux {release-version}
15 fsck.minix - check consistency of Minix filesystem
19 *fsck.minix* [options] _device_
23 *fsck.minix* performs a consistency check for the Linux MINIX filesystem.
25 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.
27 The _device_ name will usually have the following form:
32 |/dev/hda[1-63] |IDE disk 1
33 |/dev/hdb[1-63] |IDE disk 2
34 |/dev/sda[1-15] |SCSI disk 1
35 |/dev/sdb[1-15] |SCSI disk 2
39 If the filesystem was changed, i.e., repaired, then *fsck.minix* will print "FILE SYSTEM HAS BEEN CHANGED" and will *sync*(2) three times before exiting. There is _no_ need to reboot after check.
43 *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, such as the root filesystem, make sure nothing is writing to the disk, and that no files are "zombies" waiting for deletion.
51 Perform interactive repairs.
54 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.
60 Output super-block information.
63 Activate MINIX-like "mode not cleared" warnings.
66 Force a filesystem check even if the filesystem was marked as valid. Marking is done by the kernel when the filesystem is unmounted.
69 Display version information and exit.
72 Display help text and exit.
76 There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage.
78 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".
82 The exit status returned by *fsck.minix* is the sum of the following:
87 Filesystem errors corrected, system should be rebooted if filesystem was mounted
89 Filesystem errors left uncorrected
91 Combination of exit statuses 3 and 4
100 mailto:torvalds@cs.helsinki.fi[Linus Torvalds]. Exit status values by mailto:faith@cs.unc.edu[Rik Faith] Added support for filesystem valid flag: mailto:greg%wind.uucp@plains.nodak.edu[Dr. Wettstein]. Check to prevent fsck of mounted filesystem added by mailto:quinlan@yggdrasil.com[Daniel Quinlan]. Minix v2 fs support by mailto:schwab@issan.informatik.uni-dortmund.de[Andreas Schwab], updated by mailto:janl@math.uio.no[Nicolai Langfeldt]. Portability patch by mailto:rmk@ecs.soton.ac.uk[Russell King].
111 include::man-common/bugreports.adoc[]
113 include::man-common/footer.adoc[]
116 include::man-common/translation.adoc[]