Many messages can come from the check (blockget) command. If the
filesystem is completely corrupt, a core dump might be produced
instead of the message
device is not a valid filesystem
If the filesystem is very large (has many files) then check might
run out of memory. In this case the message
out of memory
is printed.
The following is a description of the most likely problems and
the associated messages. Most of the diagnostics produced are
only meaningful with an understanding of the structure of the
filesystem.
agf_freeblks n, counted m in ag a
The freeblocks count in the allocation group header for
allocation group a doesn't match the number of blocks
counted free.
agf_longest n, counted m in ag a
The longest free extent in the allocation group header for
allocation group a doesn't match the longest free extent
found in the allocation group.
agi_count n, counted m in ag a
The allocated inode count in the allocation group header
for allocation group a doesn't match the number of inodes
counted in the allocation group.
agi_freecount n, counted m in ag a
The free inode count in the allocation group header for
allocation group a doesn't match the number of inodes
counted free in the allocation group.
block a/b expected inum 0 got i
The block number is specified as a pair (allocation group
number, block in the allocation group). The block is used
multiple times (shared), between multiple inodes. This
message usually follows a message of the next type.
block a/b expected type unknown got y
The block is used multiple times (shared).
block a/b type unknown not expected
