This phase checks the inode list.
It reports error conditions encountered while:
UNKNOWN FILE TYPE I=I (CLEAR)-
The mode word of the inode I
indicates that the inode is not a
special block inode, special character inode, regular inode,
symbolic link, FIFO file, or directory inode.
Possible responses to the
CLEAR prompt are:
YES-
Deallocate inode
I
by zeroing out its contents.
This always generates the
UNALLOCATED
error message in Phase 2
for each directory entry pointing to this inode.
NO-
Ignore this error condition.
PARTIALLY TRUNCATED INODE I=I (SALVAGE)-
fsck
has found inode
I
whose size is shorter than the number of
blocks allocated to it.
This condition should only occur if the system crashes while
truncating a file.
When preening the filesystem,
fsck
completes the truncation to the specified size.
Possible responses to the
SALVAGE
prompt are:
YES-
Complete the truncation to the size specified in the inode.
NO-
Ignore this error condition.
LINK COUNT TABLE OVERFLOW (CONTINUE)-
An internal table for
fsck
containing allocated inodes with a link count of
zero has no more room.
Possible responses to the
CONTINUE
prompt are:
YES-
Continue with the program.
This error condition prevents a complete check of the filesystem.
A second run of
fsck
should be made to recheck the filesystem.
If another allocated inode with a zero link count is found,
the error message is repeated.
NO-
Terminate the program.
B BAD I=I-
Inode I
contains block number B with a number
lower than the number of the first data block in the filesystem or
greater than the number of the last block
in the filesystem.
This error condition might generate the
EXCESSIVE BAD BLKS
error message in Phase 1 if inode I
has too many block numbers outside the filesystem range.
This error condition generates the
BAD/DUP
error messages in Phases 2 and 4.
EXCESSIVE BAD BLKS I=I (CONTINUE)-
There are too many (usually more than 10) blocks with a number
lower than the number of the first data block in the filesystem or greater than
the number of the last block in the filesystem associated with
inode I.
Possible responses to the
CONTINUE
prompt are:
YES-
Ignore the rest of the blocks in this inode
and continue checking
with the next inode in the filesystem.
This error condition
prevents a complete check of the filesystem.
A second run of
fsck
should be made to recheck this filesystem.
NO-
Terminate the program.
BAD STATE DDD TO BLKERR-
An internal error has scrambled
fsck's
state map to have the impossible value DDD.
fsck
exits immediately.
If this occurs, contact your service
representative or another qualified person.
B DUP I=I-
Inode
I
contains block number B that is already claimed by
another inode.
This error condition might generate the
EXCESSIVE DUP BLKS
error message in Phase 1 if
inode
I
has too many block numbers claimed by other inodes.
This error condition invokes Phase 1B and generates the
BAD/DUP
error message in Phases 2 and 4.
BAD MODE: MAKE IT A FILE?-
This message is generated when the status of a given
inode is set to all ones, indicating filesystem damage.
This message does not indicate disk damage, unless it appears repeatedly
after
fsck -y
has been run.
A response of
y
causes
fsck
to reinitialize the inode to a reasonable value.
EXCESSIVE DUP BLKS I=I (CONTINUE)-
There are too many (usually more than 10) blocks claimed by other
inodes.
Possible responses to the
CONTINUE
prompt are:
YES-
Ignore the rest of the blocks in this inode
and continue checking with the next inode in the filesystem.
This error condition
prevents a complete check of the filesystem.
A second run of
fsck
should be made to recheck the filesystem.
NO-
Terminate the program.
DUP TABLE OVERFLOW (CONTINUE)-
An internal table in
fsck
containing duplicate block numbers has no more room.
Possible responses to the
CONTINUE
prompt are:
YES-
Continue with the program.
This error condition prevents a complete check of the filesystem.
A second run of
fsck
should be made to recheck the filesystem.
If another duplicate block is found, this error message repeats.
NO-
Terminate the program.
PARTIALLY ALLOCATED INODE I=I (CLEAR)-
Inode I
is neither allocated nor unallocated.
Possible responses to the
CLEAR
prompt are:
YES-
Deallocate inode
I
by zeroing out its contents.
NO-
Ignore this error condition.
INCORRECT BLOCK COUNT I=I (X should be Y) (CORRECT)-
The block count for inode
I
is X blocks,
but should be Y blocks.
When preening, the count is corrected.
Possible responses to the
CORRECT
prompt are:
YES-
Replace the block count of inode
I
by Y.
NO-
Ignore this error condition.