INCORRECT BLOCK COUNT I=int (should be int) CORRECT?

Cause

During phase 1, fsck(1M) determined that the specified inode pointed to a number of bad or duplicate blocks, so the block count should be corrected to the actual number shown.

Action

Generally you can answer yes to this question without harming the filesystem.

See Also

For more information on bad blocks, see the section on checking filesystem integrity in the System Administration Guide, Volume I.