View Source: fsck.minix(8) - Waikato Linux Users Group

You are viewing an old revision of this page. View the current version.

FSCK
!!!FSCK
NAME
SYNOPSIS
DESCRIPTION
WARNING
OPTIONS
SEE ALSO
DIAGNOSTICS
EXIT CODES
AUTHOR
----
!!NAME


fsck.minix - a file system consistency checker for Linux
!!SYNOPSIS


__fsck.minix [[ -larvsmf ]__ device
!!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 file system 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 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 file system was changed (i.e., repaired), then __fsck.minix__ will print sync(2) three times before exiting. Since Linux does not currently have raw devices, there is ''no'' need to reboot at this time.
!!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
__
!!OPTIONS


__-l__


Lists all filenames


__-r__


Performs interactive repairs


__-a__


Performs 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 file system damage.


__-v__


Verbose


__-s__


Outputs super-block information


__-m__


Activates MINIX-like


__-f__


Force file system check even if the file system was marked
as valid (this marking is done by the kernel when the file
system is unmounted).
!!SEE ALSO


fsck(8), __fsck.ext__(8), __fsck.ext2__(8),
__fsck.xiafs__(8), mkfs(8), __mkfs.minix__(8),
__mkfs.ext__(8), __mkfs.ext2__(8),
__mkfs.xiafs__(8). reboot(8)
!!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
__fsck.minix__
will print
__
!!EXIT CODES


The exit code returned by __fsck.minix__ is the sum of
the following:


0


No errors


3


File system errors corrected, system should be rebooted if
file system was mounted


4


File system errors left uncorrected


8


Operational error


16


Usage or syntax error


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


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

2 pages link to fsck.minix(8):

This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.

Version 1, saved on Tuesday, June 4, 2002 12:31:12 am by "perry"

Edit PageHistory Diff Info LikePages