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

fsck(IM) fsck(IM)
8. Superblock checks are perfonned for:
more than the maximum number of inodes.
more blocks for inodes than there are in the file system
9. Checks for a bad free-block list fonnat are perfonned.
10. Checks for incorrect total free block or free inode count, or
both, are perfonned.
Reconnection of dislocated files
Orphaned files and directories (allocated but unreferenced) are,
with the operator's confirmation, reconnected, if not empty, by
placing them in the lost+found directory. The user is notified
if the file or directory is empty or not. If it is empty, fsck silently
removes them and forces the reconnection of nonempty directories.
The name assigned is the inode number. The only restriction
is that the directory lost+found must preexist in the root
of the file system being checked and must have empty slots in
which entries can be made. This is accomplished by making a
lost+found directory, copying a number of files to the directory,
and then removing the files before fsck is executed. See
mklost+found(1M).
EXAMPLES
fsck /dev/rdskO/cOdOsO
checks the consistency of the file system referred through
/dev/rdskO/cOdOsO.
FILES
/etc/fsck
/etc/ufs/fsck
/etc/svfs/fsck
/etc/%fsck
/etc/fstab Contains default list of file systems to
check
SEE ALSO
cl ri(IM), f si rand(1M), mkf s(IM), ncheck(1M),
newfs(1M), typefs(IM), fstab(4), fs(4).
"Checking the NUX File System: fsck," inAIUX Local System
Administration.
DIAGNOSTICS
The diagnostics produced by fsck are intended to be selfexplanatory
.
5
February, 1990
Revision C