Troubleshooting the Cause of Solaris UFS File System Corruption and Preventing Future Corruption
(Doc ID 1009218.1)
Last updated on SEPTEMBER 17, 2020
Applies to:Solaris Operating System - Version 8.0 and later
This document tells how to diagnose the cause of data integrity issues on UFS mounted file systems, and gives advice about how to prevent future corruption.
File system corruption in Solaris can manifest itself in several ways. One way is to panic with one of these panic strings:
freeing free frag
freeing free inode
freeing free block
ufs_putapage: bn == UFS_HOLE
Another way is for messages to be recorded in /var/adm/messages prior to a system panic:
NOTICE: /: unexpected free inode ####, run fsck(1M) -o f
WARNING: /: unexpected allocated inode ####, run fsck(1M) -o f
where / is the file system the corruption occurred on and #### will be the inode number.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!