1FSCK.MINIX(8) System Administration FSCK.MINIX(8)
2
6 fsck.minix - check consistency of Minix filesystem
7
9 fsck.minix [options] device
10
12 fsck.minix performs a consistency check for the Linux MINIX filesystem.
13 The program assumes the filesystem is quiescent. fsck.minix should not
15 be used on a mounted device unless you can be sure nobody is writing to
16 it. Remember that the kernel can write to device when it searches for
17 files.
18 The device name will usually have the following form:
20 /dev/hda[1–63] IDE disk 1
22 /dev/hdb[1–63] IDE disk 2
23 /dev/sda[1–15] SCSI disk 1
24 /dev/sdb[1–15] SCSI disk 2
25 If the filesystem was changed, i.e., repaired, then fsck.minix will
27 print "FILE SYSTEM HAS CHANGED" and will sync(2) three times before
28 exiting. There is no need to reboot after check.
29
31 fsck.minix should not be used on a mounted filesystem. Using
32 fsck.minix on a mounted filesystem is very dangerous, due to the possi‐
33 bility that deleted files are still in use, and can seriously damage a
34 perfectly good filesystem! If you absolutely have to run fsck.minix on
35 a mounted filesystem, such as the root filesystem, make sure nothing is
36 writing to the disk, and that no files are "zombies" waiting for dele‐
37 tion.
38
40 -l, --list
41 List all filenames.
42 -r, --repair
44 Perform interactive repairs.
45 -a, --auto
47 Perform automatic repairs. This option implies --repair and
48 serves to answer all of the questions asked with the default.
49 Note that this can be extremely dangerous in the case of exten‐
50 sive filesystem damage.
51 -v, --verbose
53 Be verbose.
54 -s, --super
56 Output super-block information.
57 -m, --uncleared
59 Activate MINIX-like "mode not cleared" warnings.
60 -f, --force
62 Force a filesystem check even if the filesystem was marked as
63 valid. Marking is done by the kernel when the filesystem is
64 unmounted.
65 -V, --version
67 Display version information and exit.
68 -h, --help
70 Display help text and exit.
71
73 There are numerous diagnostic messages. The ones mentioned here are
74 the most commonly seen in normal usage.
75 If the device does not exist, fsck.minix will print "unable to read
77 super block". If the device exists, but is not a MINIX filesystem,
78 fsck.minix will print "bad magic number in super-block".
79
81 The exit code returned by fsck.minix is the sum of the following:
82 0 No errors
84 3 Filesystem errors corrected, system should be rebooted if
85 filesystem was mounted
86 4 Filesystem errors left uncorrected
87 7 Combination of exit codes 3 and 4
88 8 Operational error
89 16 Usage or syntax error
90
92 Linus Torvalds ⟨torvalds@cs.helsinki.fi⟩
93 Error code values by Rik Faith ⟨faith@cs.unc.edu⟩
94 Added support for filesystem valid flag: Dr. Wettstein ⟨greg%wind.uucp@
95 plains.nodak.edu⟩.
96 Check to prevent fsck of mounted filesystem added by Daniel Quinlan
97 ⟨quinlan@yggdrasil.com⟩.
98 Minix v2 fs support by Andreas Schwab ⟨schwab@issan.informatik.uni-
99 dortmund.de⟩, updated by Nicolai Langfeldt ⟨janl@math.uio.no⟩.
100 Portability patch by Russell King ⟨rmk@ecs.soton.ac.uk⟩.
101
103 fsck(8), fsck.ext2(8), mkfs(8), mkfs.ext2(8), mkfs.minix(8), reboot(8)
104
106 The fsck.minix command is part of the util-linux package and is avail‐
107 able from Linux Kernel Archive ⟨https://www.kernel.org/pub/linux/utils
108 /util-linux/⟩.
109util-linux June 2015 FSCK.MINIX(8)