Improper fsck(1M) Usage can Lead to Bogus "unexpected free/allocated inode" Messages From UFS Filesystem
Beginning with Solaris 8 kernel patch 108528-18 for SPARC(R) and 108529-18 for x86, a sanity check has been added in ufs module to check for inode inconsistency. Due to improper fsck usage these messages get emitted into system console and /var/adm/messages file: Patch 108528-18 Patch 108529-18 Without logging: "NOTICE: : unexpected free inode , run fsck(1M)" With logging enabled: "NOTICE: : unexpected free inode , run fsck(1M) -o f" There are additional sanity checks which result in seeing the following messages: Without logging: "NOTICE: : unexpected allocated inode , run fsck(1M)" With logging enabled: "NOTICE: : unexpected allocated inode , run fsck(1M) -o f" Troubleshooting Steps If the systems display the unexpected inode messages: * Check /var/adm/messages for multiple entries for the same inode number * Check to see if there are any inode entries under /lost+found directory. If the inode entry matches with t...