block-number BAD I=inode-number

Inode inode-number contains a block number block-number with a number lower than the number of the first data block in the file system or greater than the number of the last block in the file system. This error condition may generate the EXCESSIVE BAD BLKS error message in phase 1 if inode inode-number has too many block numbers outside the file system range. This error condition generates the BAD/DUP error message in phases 2 and 4.

N/A

BAD MODE: MAKE IT A FILE?

The status of a given inode is set to all 1s, indicating file system damage. This message does not indicate physical disk damage, unless it is displayed repeatedly after fsck -y has been run.

Type y to reinitialize the inode to a reasonable value.

BAD STATE state-number TO BLKERR

An internal error has scrambled the fsck state map so that it shows the impossible value state-number. fsck exits immediately.

Contact your local service provider or another qualified person. 

block-number DUP I=inode-number

Inode inode-number contains a block number block-number, which is already claimed by the same or another inode. This error condition may generate the EXCESSIVE DUP BLKS error message in phase 1 if inode inode-number has too many block numbers claimed by the same or another inode. This error condition invokes phase 1B and generates the BAD/DUP error messages in phases 2 and 4.

N/A 

DUP TABLE OVERFLOW (CONTINUE)

There is no more room in an internal table in fsck containing duplicate block numbers. If the -o p option is specified, the program terminates.

To continue the program, type y at the CONTINUE prompt. When this error occurs, a complete check of the file system is not possible. If another duplicate block is found, this error condition repeats. Increase the amount of virtual memory available (by killing some processes, increasing swap space) and run fsck again to recheck the file system. To terminate the program, type n.

EXCESSIVE BAD BLOCKS I=inode-number (CONTINUE)

Too many (usually more than 10) blocks have a number lower than the number of the first data block in the file system or greater than the number of the last block in the file system associated with inode inode-number. If the -o p (preen) option is specified, the program terminates.

To continue the program, type y at the CONTINUE prompt. When this error occurs, a complete check of the file system is not possible. You should run fsck again to recheck the file system. To terminate the program, type n.

EXCESSIVE DUP BLKS I=inode-number (CONTINUE)

Too many (usually more than 10) blocks are claimed by the same or another inode or by a free-list. If the -o p option is specified, the program terminates.

To continue the program, type y at the CONTINUE prompt. When this error occurs, a complete check of the file system is not possible. You should run fsck again to recheck the file system. To terminate the program, type n.

INCORRECT BLOCK COUNT I=inode-number (number-of-BAD-DUP-or-missing-blocks should be 
number-of-blocks-in-filesystem) (CORRECT)

The block count for inode inode-number is number-of-BAD-DUP-or-missing-blocks, but should be number-of-blocks-in-filesystem. When preening, fsck corrects the count.

To replace the block count of inode inode-number by number-of-blocks-in-filesystem, type y at the CORRECT prompt. To terminate the program, type n.

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. If the -o p (preen) option is specified, the program exits and fsck has to be completed manually.

To continue the program, type y at the CONTINUE prompt. If another allocated inode with a zero-link count is found, this error condition repeats. When this error occurs, a complete check of the file system is not possible. You should run fsck again to recheck the file system. Increase the virtual memory available by killing some processes or increasing swap space, then run fsck again. To terminate the program, type n.

PARTIALLY ALLOCATED INODE I=inode-number (CLEAR)

Inode inode-number is neither allocated nor unallocated. If the -o p (preen) option is specified, the inode is cleared.

To deallocate the inode inode-number by zeroing out its contents, type y. This may generate the UNALLOCATED error condition in phase 2 for each directory entry pointing to this inode.To ignore the error condition, type n. A no response is appropriate only if you intend to take other measures to fix the problem.

PARTIALLY TRUNCATED INODE I=inode-number (SALVAGE)

fsck has found inode inode-number whose size is shorter than the number of blocks allocated to it. This condition occurs only if the system crashes while truncating a file. When preening the file system, fsck completes the truncation to the specified size.

To complete the truncation to the size specified in the inode, type y at the SALVAGE prompt. To ignore this error condition, type n.

UNKNOWN FILE TYPE I=inode-number (CLEAR)

The mode word of the inode inode-number shows that the inode is not a pipe, special character inode, special block inode, regular inode, symbolic link, FIFO file, or directory inode. If the -o p option is specified, the inode is cleared.

To deallocate the inode inode-number by zeroing its contents, which results in the UNALLOCATED error condition in phase 2 for each directory entry pointing to this inode, type y at the CLEAR prompt. To ignore this error condition, type n.