Veritas File System 5.1 SP1 Administrator"s Guide (5900-1499, April 2011)

Description:
When inode information is no longer dependable, the kernel marks it bad on disk.
The most common reason for marking an inode bad is a disk I/O failure. If there
is an I/O failure in the inode list, on a directory block, or an indirect address extent,
the integrity of the data in the inode, or the data the kernel tried to write to the
inode list, is questionable. In these cases, the disk driver prints an error message
and one or more inodes are marked bad.
The kernel also marks an inode bad if it finds a bad extent address, invalid inode
fields, or corruption in directory data blocks during a validation check. A validation
check failure indicates the file system has been corrupted. This usually occurs
because a user or process has written directly to the device or used fsdb to change
the file system.
The VX_FULLFSCK flag is set in the super-block so fsck will do a full structural
check the next time it is run.
Recommended action:
Check the console log for I/O errors. If the problem is a disk failure, replace the
disk. If the problem is not related to an I/O failure, find out how the disk became
corrupted. If no user or process is writing to the device, report the problem to
your customer support organization. In either case, unmount the file system and
use fsck to run a full structural check.
V-2-80
WARNING: msgcnt x: vxfs: mesg 080: Disk layout versions older than Version 4
will not be supported in the next release. It is advisable to upgrade to the latest
disk layout version now.
See the vxupgrade(1M) manual page.
See the Veritas Storage Foundation Release Notes.
Recommended action:
Use the vxupgrade command to begin upgrading file systems using older disk
layouts to Version 5, then 6, then 7. Consider the following when planning disk
layout upgrades:
Version 2 disk layout file systems have an 8 million inode limit.
Images of Version 2 disk layout file systems created by copy utilities, such as dd
or volcopy, will become unusable after a disk layout upgrade.
Diagnostic messages
Dewey kernel messages
216