FSCK.MINIX(8) System Administration FSCK.MINIX(8)
fsck.minix - check consistency of Minix filesystem
fsck.minix [options] device
fsck.minix performs a consistency check for the Linux MINIX filesystem. 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.
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.
-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.
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 in super-block".
The exit code returned by fsck.minix is the sum of the following: 0 No errors 3 Filesystem errors corrected, system should be rebooted if filesystem was mounted 4 Filesystem errors left uncorrected 7 Combination of exit codes 3 and 4 8 Operational error 16 Usage or syntax error
Linus Torvalds ⟨email@example.com⟩ Error code values by Rik Faith ⟨firstname.lastname@example.org⟩ Added support for filesystem valid flag: Dr. Wettstein ⟨greg%wind. email@example.com⟩. Check to prevent fsck of mounted filesystem added by Daniel Quinlan ⟨firstname.lastname@example.org⟩. Minix v2 fs support by Andreas Schwab ⟨email@example.com- dortmund.de⟩, updated by Nicolai Langfeldt ⟨firstname.lastname@example.org⟩. Portability patch by Russell King ⟨email@example.com⟩.
fsck(8), fsck.ext2(8), mkfs(8), mkfs.ext2(8), mkfs.minix(8), reboot(8)
The fsck.minix command is part of the util-linux package and is available from Linux Kernel Archive ⟨https://www.kernel.org/pub/linux/utils/util-linux/⟩.
This page is part of the util-linux (a random collection of Linux utilities) project. Information about the project can be found at ⟨https://www.kernel.org/pub/linux/utils/util-linux/⟩. If you have a bug report for this manual page, send it to firstname.lastname@example.org. This page was obtained from the project's upstream Git repository ⟨git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git⟩ on 2017-04-25. If you discover any rendering problems in this HTML ver‐ sion of the page, or you believe there is a better or more up-to-date source for the page, or you have corrections or improvements to the information in this COLOPHON (which is not part of the original man‐ ual page), send a mail to email@example.com util-linux June 2015 FSCK.MINIX(8)
Pages that refer to this page: fsck(8@@e2fsprogs), fsck(8), systemd-fsck@.service(8)