fsck.minix

check consistency of Minix filesystem

see also : fsck - fsck.ext2 - mkfs - mkfs.minix - mkfs.ext2 - reboot

Synopsis

fsck.minix [-larvsmf] device

add an example, a script, a trick and tips

: email address (won't be displayed)
: name

Step 2

Thanks for this example ! - It will be moderated and published shortly.

Feel free to post other examples Oops ! There is a tiny cockup. A damn 404 cockup. Please contact the loosy team who maintains and develops this wonderful site by clicking in the mighty feedback button on the side of the page. Say what happened. Thanks!

examples

source

            
  find findfs fold free freeramdisk fsck
  fsck.minix fsync ftpd ftpget ftpput


  fuser getopt getty grep gunzip gzip halt hd
  hdparm head hexdump hostid

description

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:

/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. Since Linux does not currently have raw devices, there is no need to reboot at this time.

options

-l

List all filenames.

-r

Perform interactive repairs.

-a

Perform automatic repairs. (This option implies -r 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

Be verbose.

-s

Output super-block information.

-m

Activate MINIX-like "mode not cleared" warnings.

-f

Force a filesystem check even if the filesystem was marked as valid (this marking is done by the kernel when the filesystem is unmounted).

availability

The fsck.minix command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/.

diagnostics

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".

exit codes

The exit code returned by fsck.minix is the sum of the following:

No errors

Filesystem errors corrected, system should be rebooted if filesystem was mounted

Filesystem errors left uncorrected

Operational error

Usage or syntax error

In point of fact, only 0, 3, 4, 7, 8, and 16 can ever be returned.

warning

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.

see also

fsck , fsck.ext, fsck.ext2 , fsck.xiafs, mkfs , mkfs.minix , mkfs.ext, mkfs.ext2 , mkfs.xiafs, reboot

author

Linus Torvalds (torvalds[:at:]cs.helsinki[:dot:]fi)
Error code values by Rik Faith (faith[:at:]cs.unc[:dot:]edu)
Added support for filesystem valid flag: Dr. Wettstein (greg%wind.uucp[:at:]plains.nodak[:dot:]edu)
Check to prevent fsck of mounted filesystem added by Daniel Quinlan (quinlan[:at:]yggdrasil[:dot:]com)
Minix v2 fs support by Andreas Schwab (schwab[:at:]issan.informatik[:dot:]uni-dortmund.de), updated by Nicolai Langfeldt (janl[:at:]math.uio[:dot:]no)
Portability patch by Russell King (rmk[:at:]ecs.soton.ac[:dot:]uk).