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.

There is no more room in an internal table for fsck containing allocated inodes with a link count of zero.

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.

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.

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.

There is more than a tolerable number (usually 50) of blocks claimed by other inodes.

There is no more room in an internal table in fsck containing duplicate block numbers.

Inode I is neither allocated nor unallocated.

The number of extents is larger than the maximum the system can set and is therefore ridiculous.

The number of extents or pointers to extents (indirect extents) exceeds the number of slots in the inode for describing extents.

The pointer to an extent contains a “magic number.” If this number is invalid, the pointer to the extent is probably corrupt.

An extent's idea of where it is in the file is inconsistent with the extent pointer in relation to other extent pointers.

An extent is zero length.

It is erroneous for a directory inode to claim a size of zero. The corresponding inode is cleared.

A directory's size must be an integer number of blocks. The size is recomputed based on its extents.

If the computation of size (above) fails, fsck prints this message and asks to clear the inode.

The number of extents or pointers to extents (indirect extents) exceeds the number of slots in the inode for describing extents.

The number of blocks in the directory computed from extent pointer lengths is inconsistent with the number computed from the inode size field.

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.

Inode I contains block number B, which is already claimed by another inode. This error condition invokes the BAD/DUP error condition in Phase 2. Inodes with overlapping blocks may be determined by examining this error condition and the DUP error condition in Phase 1.

The root inode points to incorrect information. There is no way to fix this problem, so the command stops.

If this problem occurs on the Root filesystem, you must reinstall IRIX. If it occurs on another filesystem, you must recreate the filesystem using mkfs and recover files and data from backups.

The root directory inode does not seem to describe a directory. This error is usually fatal. The typical answer is yes.

Something is wrong with the block addressing information of the root directory. The typical answer is yes.

A directory entry F has an inode number I that is greater than the end of the inode list. The typical answer is yes.

A directory entry F has an inode I that is not marked as allocated. The owner O, mode M, size S, modify time T, and filename F are printed. If the filesystem is not mounted and the -n option is not specified, and if the inode that the entry points to is size 0, the entry is removed automatically.

Phase 1 or Phase 1B found duplicate blocks or bad blocks associated with directory entry F, directory inode I. The owner O, mode M, size S, modify time T, and directory name F are printed. 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.

Phase 1 or Phase 1B found duplicate blocks or bad blocks associated with file entry F, inode I. The owner O, mode M, size S, modify time T, and filename F are printed. 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.

The directory inode I was not connected to a directory entry when the filesystem was traversed. The owner O, mode M, size S, and modify time T of directory inode I are printed. The fsck command forces the reconnection of a nonempty directory. The typical answer is yes.

No lost+found directory is in the root directory of the filesystem; fsck ignores the request to link a directory in lost+found. The unreferenced file is removed.

Use fsck -l to recover and remake the lost+found directory as soon as possible.

There is no space to add another entry to the lost+found directory in the root directory of the filesystem; fsck ignores the request to link a directory in lost+found. The unreferenced file is removed.

Use fsck -l to recover and clean out the lost+found directory as soon as possible.

This is an advisory message indicating that a directory inode I1 was successfully connected to the lost+found directory. The parent inode I2 of the directory inode I1 is replaced by the inode number of the lost+found directory.

Inode I was not connected to a directory entry when the filesystem was traversed. The owner O, mode M, size S, and modify time T of inode I are printed. If the -n option is omitted and the filesystem is not mounted, empty files are cleared automatically. Nonempty files are not cleared.

There is no lost+found directory in the root directory of the filesystem; fsck ignores the request to link a file in lost+found.

Use fsck -l to recover and create the lost+found directory as soon as possible.

There is no space to add another entry to the lost+found directory in the root directory of the filesystem; fsck ignores the request to link a file in lost+found.

Use fsck -l to recover and clean out the lost+found directory as soon as possible.

The inode mentioned in the immediately previous UNREF error condition cannot be reconnected, so it is cleared.

The link count for inode I, which is a file, is X but should be Y. The owner O, mode M, size S, and modify time T are printed.

The link count for inode I, which is a directory, is X but should be Y. The owner O, mode M, size S, and modify time T of directory inode I are printed.

The link count for F inode I is X but should be Y. The filename F, owner O, mode M, size S, and modify time T are printed.

Inode I, which is a file, was not connected to a directory entry when the filesystem was traversed. The owner O, mode M, size S, and modify time T of inode I are printed. If the -n option is omitted and the filesystem is not mounted, empty files are cleared automatically. Nonempty directories are not cleared. 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.

Inode I, which is a directory, was not connected to a directory entry when the filesystem was traversed. The owner O, mode M, size S, and modify time T of inode I are printed. If the -n option is omitted and the filesystem is not mounted, empty directories are cleared automatically. Nonempty directories are not cleared. 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.

Phase 1 or Phase 1B found duplicate blocks or bad blocks associated with file inode I. The owner O, mode M, size S, and modify time T of inode I are printed. 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.

Phase 1 or Phase 1B found duplicate blocks or bad blocks associated with directory inode I. The owner O, mode M, size S, and modify time T of inode I are printed. 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.

The actual count of the free inodes does not match the count in the superblock of the filesystem.

The actual count of free blocks does not match the count in the superblock of the filesystem.

This message is always preceded by one or more of the Phase 5 information messages.

This is an advisory message indicating that the filesystem checked contained X files using Y blocks leaving Z blocks free in the filesystem.

A field in the superblock is queried by system commands to decide if fsck must be run before mounting a filesystem. If this field is not “clean,” fsck reports and asks if it should be cleaned.

If the primary superblock is too corrupt to use, and fsck can locate a secondary superblock, it asks to replace the primary superblock with the backup.

If there is no secondary superblock, and fsck finds space for one (after the last cylinder group), it asks to create a secondary superblock.

An incorrect checksum makes a filesystem unmountable.

This is an advisory message indicating that the current filesystem was modified by fsck.

This is an advisory message indicating that fsck made changes to a mounted Root filesystem. The automatic remount ensures that in-core data structures and the filesystem are consistent.