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 ┌───────────────┬─────────────┐
22 │ │ │
23 │/dev/hda[1-63] │ IDE disk 1 │
24 ├───────────────┼─────────────┤
25 │ │ │
26 │/dev/hdb[1-63] │ IDE disk 2 │
27 ├───────────────┼─────────────┤
28 │ │ │
29 │/dev/sda[1-15] │ SCSI disk 1 │
30 ├───────────────┼─────────────┤
31 │ │ │
32 │/dev/sdb[1-15] │ SCSI disk 2 │
33 └───────────────┴─────────────┘
34 If the filesystem was changed, i.e., repaired, then fsck.minix
36 will print "FILE SYSTEM HAS BEEN CHANGED" and will sync(2) three
37 times before exiting. There is no need to reboot after check.
38
40 fsck.minix should not be used on a mounted filesystem. Using
41 fsck.minix on a mounted filesystem is very dangerous, due to the
42 possibility that deleted files are still in use, and can
43 seriously damage a perfectly good filesystem! If you absolutely
44 have to run fsck.minix on a mounted filesystem, such as the root
45 filesystem, make sure nothing is writing to the disk, and that no
46 files are "zombies" waiting for deletion.
47
49 -l, --list
50 List all filenames.
51 -r, --repair
53 Perform interactive repairs.
54 -a, --auto
56 Perform automatic repairs. This option implies --repair and
57 serves to answer all of the questions asked with the default.
58 Note that this can be extremely dangerous in the case of
59 extensive filesystem damage.
60 -v, --verbose
62 Be verbose.
63 -s, --super
65 Output super-block information.
66 -m, --uncleared
68 Activate MINIX-like "mode not cleared" warnings.
69 -f, --force
71 Force a filesystem check even if the filesystem was marked as
72 valid. Marking is done by the kernel when the filesystem is
73 unmounted.
74 -h, --help
76 Display help text and exit.
77 -V, --version
79 Print version and exit.
80
82 There are numerous diagnostic messages. The ones mentioned here
83 are the most commonly seen in normal usage.
84 If the device does not exist, fsck.minix will print "unable to
86 read super block". If the device exists, but is not a MINIX
87 filesystem, fsck.minix will print "bad magic number in
88 super-block".
89
91 The exit status returned by fsck.minix is the sum of the
92 following:
93 0
95 No errors
96 3
98 Filesystem errors corrected, system should be rebooted if
99 filesystem was mounted
100 4
102 Filesystem errors left uncorrected
103 7
105 Combination of exit statuses 3 and 4
106 8
108 Operational error
109 16
111 Usage or syntax error
112
114 Linus Torvalds <torvalds@cs.helsinki.fi>. Exit status values by
115 Rik Faith <faith@cs.unc.edu> Added support for filesystem valid
116 flag: Dr. Wettstein <greg%wind.uucp@plains.nodak.edu>. Check to
117 prevent fsck of mounted filesystem added by Daniel Quinlan
118 <quinlan@yggdrasil.com>. Minix v2 fs support by Andreas Schwab
119 <schwab@issan.informatik.uni-dortmund.de>, updated by Nicolai
120 Langfeldt <janl@math.uio.no>. Portability patch by Russell King
121 <rmk@ecs.soton.ac.uk>.
122
124 fsck(8), fsck.ext2(8), mkfs(8), mkfs.ext2(8), mkfs.minix(8),
125 reboot(8)
126
128 For bug reports, use the issue tracker at
129 https://github.com/util-linux/util-linux/issues.
130
132 The fsck.minix command is part of the util-linux package which
133 can be downloaded from Linux Kernel Archive
134 <https://www.kernel.org/pub/linux/utils/util-linux/>.
135util-linux 2.38.1 2022-05-11 FSCK.MINIX(8)