Section: System Administration (8)
Updated: July 1996
fsck.minix performs a consistency check for the Linux MINIX filesystem. The current version supports the 14 character and 30 character filename options.
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 (and remember that the kernel can write to it when it searches for files).
The device name will usually have the following form:
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. Since Linux does not currently have raw devices, there is no need to reboot at this time.
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 (i.e., the root filesystem), make sure nothing is writing to the disk, and that no files are "zombies" waiting for deletion.
There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage.
The exit code returned by fsck.minix is the sum of the following:
Linus Torvalds (email@example.com)
Error code values by Rik Faith (firstname.lastname@example.org)
Added support for filesystem valid flag: Dr. Wettstein (email@example.com)
Check to prevent fsck of mounted filesystem added by Daniel Quinlan (firstname.lastname@example.org)
Portability patch by Russell King (email@example.com).
The fsck.minix command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
Tutoriais de Tecnologia Web