Sun Microsystems Sun Workstation 100U System Manager's Manual page 312

Fsck - UNIX File System Checker Fsck Error Conditions
Possible responses to the ADJUST prompt are:
YES
replace the link count of inode I
with Y.
NO ignore this error condition.
UNREF FILE 1=1 OWNER =
0
MODE==M SIZE=S MTIME==
T
(CLEAR)
Inode I which is a file, was not connected to a directory entry when the file system was
traversed. The owner 0, mode M, size S, and modify time T of inode I are printed. When
preen'ing, this is a file that was not connected because its size or link count was zero, hence it is
cleared.
Possible responses to the CLEAR prompt are:
YES
de-allocate inode I by zeroing its contents.
NO ignore this error condition.
UNREF Dm 1=1 OWNER = 0 MODE==M SIZE==S MTIME== T (CLEAR)
Inode I which is a directory, was not connected to a directory entry when the file system was
traversed. The owner 0, mode M, size S, and modify time T of inode I are printed. When
preen'ing, this is a directory that was not connected because its size or link count was zero,
hence it is cleared.
Possible responses to the CLEAR prompt are:
YES
de-allocate inode I by zeroing its contents.
NO ignore this error condition.
BAD/DUP FILE
1=1
OWNER =
0
MODE==MSlZE=SMTIME=T (CLEAR)
Phase 1 or Phase 1 b have found duplicate blocks or bad blocks associated with file inode I. The
owner 0, mode M, size S, and modify time T of inode I are printed. This error cannot arise
when the file system is being preen'ed, as it would have caused a fatal error earlier.
Possible responses to the CLEAR prompt are:
YES
de-allocate inode I by zeroing its contents.
NO ignore this error condition.
BAD/DUP Dm 1=1 OWNER= 0 MODE==M SIZE==S MTIME== T (CLEAR)
Phase 1 or Phase 1 b have found duplicate blocks or bad blocks associated with directory inode
I. The owner 0, mode M, size S, and modify time T of inode I are printed. This error cannot
arise when the file system is being preen'ed, as it would have caused a fatal error earlier.
Possible responses to the CLEAR prompt are:
YES
de-allocate inode I by zeroing its contents.
NO ignore this error condition.
FREE INODE COUNT WRONG IN SUPERBLK (FIX)
The actual count of the free inodes does not match the count in the super-block of the file
28 July 1983
17