SYNOPSIS<\/a>
DESCRIPTION<\/a>
WARNING<\/a>
OPTIONS<\/a>
DIAGNOSTICS<\/a>
EXIT STATUS<\/a>
AUTHORS<\/a>
SEE ALSO<\/a>
AVAILABILITY<\/a> <\/p>\n
\n
NAME <\/a> <\/h2>\nfsck.minix \u2212 check consistency of Minix filesystem<\/p>\n
SYNOPSIS <\/a> <\/h2>\nfsck.minix<\/b> [options] device<\/i><\/p>\nDESCRIPTION <\/a> <\/h2>\nfsck.minix<\/b><\/i> performs a consistency check for the Linux MINIX filesystem.<\/p>\n
The program assumes the filesystem is quiescent. fsck.minix<\/b> 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.<\/p>\n
The device<\/i> name will usually have the following form:<\/p>\n
![\"Image](\"grohtml-1181981.png\")
<\/p>\n
If the filesystem was changed, i.e., repaired, then fsck.minix<\/b> will print “FILE SYSTEM HAS CHANGED” and will sync<\/b>(2) three times before exiting. There is no<\/i> need to reboot after check.<\/p>\nWARNING <\/a> <\/h2>\nfsck.minix<\/b> should not<\/b> be used on a mounted filesystem. Using fsck.minix<\/b> 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<\/b> 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.<\/p>\nOPTIONS <\/a> <\/h2>\n\u2212l<\/b>, \u2212\u2212list<\/b><\/p>\n
List all filenames.<\/p>\n
\u2212r<\/b>, \u2212\u2212repair<\/b><\/p>\n
Perform interactive repairs.<\/p>\n
\u2212a<\/b>, \u2212\u2212auto<\/b><\/p>\n
Perform automatic repairs. This option implies \u2212\u2212repair<\/b> 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.<\/p>\n
\u2212v<\/b>, \u2212\u2212verbose<\/b><\/p>\n
Be verbose.<\/p>\n
\u2212s<\/b>, \u2212\u2212super<\/b><\/p>\n
Output super-block information.<\/p>\n
\u2212m<\/b>, \u2212\u2212uncleared<\/b><\/p>\n
Activate MINIX-like “mode not cleared” warnings.<\/p>\n
\u2212f<\/b>, \u2212\u2212force<\/b><\/p>\n
Force a filesystem check even if the filesystem was marked as valid. Marking is done by the kernel when the filesystem is unmounted.<\/p>\n
\u2212V<\/b>, \u2212\u2212version<\/b><\/p>\n
Display version information and exit.<\/p>\n
\u2212h<\/b>, \u2212\u2212help<\/b><\/p>\n
Display help text and exit.<\/p>\n
DIAGNOSTICS <\/a> <\/h2>\nThere are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage.<\/p>\n
If the device does not exist, fsck.minix<\/b> will print “unable to read super block”. If the device exists, but is not a MINIX filesystem, fsck.minix<\/b> will print “bad magic number in super-block”.<\/p>\nEXIT STATUS <\/a> <\/h2>\nThe exit status returned by fsck.minix<\/b> is the sum of the following:<\/p>\n
fsck.minix<\/b> [options] device<\/i><\/p>\n fsck.minix<\/b><\/i> performs a consistency check for the Linux MINIX filesystem.<\/p>\n The program assumes the filesystem is quiescent. fsck.minix<\/b> 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.<\/p>\n The device<\/i> name will usually have the following form:<\/p>\n If the filesystem was changed, i.e., repaired, then fsck.minix<\/b> will print “FILE SYSTEM HAS CHANGED” and will sync<\/b>(2) three times before exiting. There is no<\/i> need to reboot after check.<\/p>\n fsck.minix<\/b> should not<\/b> be used on a mounted filesystem. Using fsck.minix<\/b> 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<\/b> 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.<\/p>\n \u2212l<\/b>, \u2212\u2212list<\/b><\/p>\n List all filenames.<\/p>\n \u2212r<\/b>, \u2212\u2212repair<\/b><\/p>\n Perform interactive repairs.<\/p>\n \u2212a<\/b>, \u2212\u2212auto<\/b><\/p>\n Perform automatic repairs. This option implies \u2212\u2212repair<\/b> 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.<\/p>\n \u2212v<\/b>, \u2212\u2212verbose<\/b><\/p>\n Be verbose.<\/p>\n \u2212s<\/b>, \u2212\u2212super<\/b><\/p>\n Output super-block information.<\/p>\n \u2212m<\/b>, \u2212\u2212uncleared<\/b><\/p>\n Activate MINIX-like “mode not cleared” warnings.<\/p>\n \u2212f<\/b>, \u2212\u2212force<\/b><\/p>\n Force a filesystem check even if the filesystem was marked as valid. Marking is done by the kernel when the filesystem is unmounted.<\/p>\n \u2212V<\/b>, \u2212\u2212version<\/b><\/p>\n Display version information and exit.<\/p>\n \u2212h<\/b>, \u2212\u2212help<\/b><\/p>\n Display help text and exit.<\/p>\n There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage.<\/p>\n If the device does not exist, fsck.minix<\/b> will print “unable to read super block”. If the device exists, but is not a MINIX filesystem, fsck.minix<\/b> will print “bad magic number in super-block”.<\/p>\n The exit status returned by fsck.minix<\/b> is the sum of the following:<\/p>\nDESCRIPTION <\/a> <\/h2>\n
<\/p>\nWARNING <\/a> <\/h2>\n
OPTIONS <\/a> <\/h2>\n
DIAGNOSTICS <\/a> <\/h2>\n
EXIT STATUS <\/a> <\/h2>\n