fsck_s5 Phase 1: Check Blocks and Sizes
This phase checks the inode list.
It reports error conditions encountered while:
-
checking inode types
-
setting up the zero-link-count table
-
examining inode block numbers for bad or duplicate blocks
-
checking inode size
-
checking inode format
Types of error messages--fsck_s5 Phase 1
Phase 1 produces four types of error messages:
-
Informational messages.
There is a connection between
some informational messages and messages with a
CONTINUE?
prompt. The
CONTINUE?
prompt generally indicates that
some limit has been reached.
-
messages with a
CONTINUE?
prompt, which can be responded to
as follows:
n (no)-
Terminate the program.
y (yes)-
Continue with the program.
When this error occurs a complete check of the filesystem
is not possible.
A second run of
fsck(1M)
should be made to recheck the filesystem.
-
Messages with a
CLEAR?
prompt, which can be responded
to as follows:
n (no)-
Ignore the error condition.
A no response is appropriate only if
the user intends to take other measures to fix the problem.
y (yes)-
Deallocate the inode I by zeroing out its contents.
This might generate the
UNALLOCATED
error condition in Phase 2
for each directory entry pointing to this inode.
-
Messages with a
RECOVER?
prompt, which can be responded
to as follows:
n (no)-
Recover all the blocks to which the inode points.
A no response is only appropriate if the user intends to
delete the excess blocks.
fsck_s5 Phase 1 error messages
UNKNOWN FILE TYPE I=
I (CLEAR?)
-
The mode word of the inode
I
indicates that the inode is not a
pipe, special character inode, regular inode, or directory
inode.
If the
-p
option is specified the inode is cleared.
LINK COUNT TABLE OVERFLOW (CONTINUE?)
-
An internal table for
fsck
containing allocated inodes
with a link count of zero has no more room.
If the -p
option is specified the program exits and
fsck must be completed manually.
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 BLOCKS
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 message in Phases 2 and 4.
EXCESSIVE BAD BLOCKS 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. If the -p
option is specified the program terminates.
B DUP I=
I-
Inode I
contains block number B, which is already claimed by
the same or another inode or by a free list.
This error condition might generate the
EXCESSIVE DUP BLKS
error message in Phase 1 if
inode I has too many block numbers
claimed by the same or another inode or by a free list.
This error condition invokes Phase 1B and
generates the BAD/DUP
error messages in Phases 2 and 4.
EXCESSIVE DUP BLKS I=
I (CONTINUE?)
-
There are too many (usually more than 10) blocks claimed
by the same or another inode or by a free list.
If the
-p
option is specified the program terminates.
DUP TABLE OVERFLOW (CONTINUE?)
-
An internal table in
fsck
containing duplicate block numbers has no more room.
If the
-p
option is specified the program terminates.
DIRECTORY MISALIGNED I=
I-
The size of a directory inode is not a multiple of 16.
If the
-p
option is used, the directory
is recovered automatically.
PARTIALLY ALLOCATED INODE I=
I (CLEAR?)
-
Inode I
is neither allocated nor unallocated.
If the -p
option is specified the inode is cleared.
DIR/FILE SIZE ERROR
-
The file references more or less data
than is indicated by the inode.
DELETE OR RECOVER EXCESS DATA
-
The user has the choice of
deleting or recovering the excess blocks pointed
to by the inode.
RECOVER?
-
The file references more data than is indicated by the inode.
The user is given the choice of correcting
the inode information.
If the
-p
option is specified the data is recovered.
DELETE?
-
The file references more data than is indicated by
the inode.
The user is given the choice of deleting
the referenced blocks and leaving the inode data intact.
© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 22 April 2004