My Oracle Support Banner

Troubleshooting the Cause of Solaris UFS File System Corruption and Preventing Future Corruption (Doc ID 1009218.1)

Last updated on JANUARY 02, 2018

Applies to:

Solaris Operating System - Version 8.0 and later
All Platforms

Purpose

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
or
ufs_putapage: bn == UFS_HOLE


NOTE: It is possible to prevent the system from panicking as a result of file system corruption; instead you can make the system unmount or lock the corrupted file system. For more information please see the mount_ufs(1M) man page, specifically the "onerror" option which allows you to change the default (panic) behavior when file system corruption occurs.



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.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.