Phase 1 Error Messages

Phase 1 Error Messages

Phase 1 has three types of error messages: information messages, messages with a CONTINUE? prompt, and messages with a CLEAR? prompt. The responses that you give to phase 1 prompts affect fsck functions. The possible responses are discussed in the next section, "Phase 1 Responses." Typically, the right answer is yes, except as noted.

UNKNOWN FILE TYPE I=I (CLEAR?): The mode word of the inode I suggests that the inode is not a pipe, special character inode, regular inode, directory inode, symbolic link, or socket.
LINK COUNT TABLE OVERFLOW (CONTINUE?): There is no more room in an internal table for fsck containing allocated inodes with a link count of zero.
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 may invoke the EXCESSIVE BAD BLKS error condition in Phase 1 if inode I has too many block numbers outside the filesystem range. This error condition invokes the BAD/DUP error condition in Phase 2 and Phase 4.
EXCESSIVE BAD BLOCKS I=I (CONTINUE?): There is more than a tolerable number (usually 50) of 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.
B DUP I=I: Inode I contains block number B, which is already claimed by another inode. This error condition may invoke the EXCESSIVE DUP BLKS error condition in Phase 1 if inode I has too many block numbers claimed by other inodes. This error condition invokes Phase 1B and the BAD/DUP error condition in Phase 2 and Phase 4. Typically, you should answer no the first time this error appears and yes the second time if you know the files claimed by the other inode.
EXCESSIVE DUP BLKS I=I (CONTINUE?): There is more than a tolerable number (usually 50) of blocks claimed by other inodes.
DUP TABLE OVERFLOW (CONTINUE?): There is no more room in an internal table in fsck containing duplicate block numbers.
PARTIALLY ALLOCATED INODE I=I (CLEAR?): Inode I is neither allocated nor unallocated.
RIDICULOUS NUMBER OF EXTENTS (n) (max allowed n): The number of extents is larger than the maximum the system can set and is therefore ridiculous.
ILLEGAL NUMBER OF INDIRECT EXTENTS (n): The number of extents or pointers to extents (indirect extents) exceeds the number of slots in the inode for describing extents.
BAD MAGIC IN EXTENT: The pointer to an extent contains a "magic number." If this number is invalid, the pointer to the extent is probably corrupt.
EXTENT OUT OF ORDER: An extent's idea of where it is in the file is inconsistent with the extent pointer in relation to other extent pointers.
ZERO LENGTH EXTENT: An extent is zero length.
ZERO SIZE DIRECTORY: It is erroneous for a directory inode to claim a size of zero. The corresponding inode is cleared.
DIRECTORY SIZE ERROR: A directory's size must be an integer number of blocks. The size is recomputed based on its extents.
DIRECTORY EXTENTS CORRUPTED: If the computation of size (above) fails, fsck prints this message and asks to clear the inode.
NUMBER OF EXTENTS TOO LARGE: The number of extents or pointers to extents (indirect extents) exceeds the number of slots in the inode for describing extents.
POSSIBLE DIRECTORY SIZE ERROR: The number of blocks in the directory computed from extent pointer lengths is inconsistent with the number computed from the inode size field.
POSSIBLE FILE SIZE ERROR: The number of blocks in the file computed from extent pointer lengths is inconsistent with the number computed from the inode size field. fsck gives the option of clearing the inode in this case.