A/UX® System Administrator's Reference Sections 1M, 7, and 8

fsck(IM) fsck(IM)
NAME
fsck - check file-system consistency and interactively repair
SYNOPSIS
/ etc/ fsck -T 5.2 [-y] [-n] [-mtimeout] [-sX] [-SX]
[-tjile] [-q] [-Doptions ... ] [-f] [-ppasstostart]
[svfs-jilesystem . .. ]
/etc/fsck [-bblock-number] [-y] [-n] [-mtimeout] -T 4.2
[-ppasstostart] [ufs-filesystem ... ]
DESCRIPTION
fsck audits and interactively repairs inconsistent conditions for
A/UX® file systems. Iffilesystem is not specified, fsck reads a
list of default file systems from the file / et c / f stab. If the file
system is consistent, then only the number of files, number of
blocks used, and number of blocks free are reported. If the file
system is inconsistent, the operator is prompted for confirmation
to proceed before each corrective action is attempted. Frequently
corrective actions result in some loss of data. The amount and
severity of data lost may be determined by examining various
parameters such as non-zero filesize. Typically, each consistency
correction is gated by the operator's yes or no response. However,
if the operator does not have write permission for jilesystem,
fsck merely indicates corrective actions needed.
fsck has more consistency checks than its predecessors check,
dcheck, fcheck, and icheck combined.
Checking the raw device is almost always faster and should be
used with everything but the root file system. In addition, any file
system other than the root file system should be unmounted at the
time that it is checked with fsck. (It is not possible to un mount
the root file system.)
FLAG OPTIONS
The flag options for the f s c k command differ depending on the
type of file system.
1
The following flag options apply to both System V file systems
(SVFS) and Berkeley 4.2 file systems (UFS):
-Tjile-system-type
Indicate the file-system type, for example, 4. 2 for a
Berkeley 4.2 file system (UFS) or 5 . 2 for a SVFS file system.
If this option is not used, f sck attempts to determine
the type.
February, 1990
Revision C