Veritas File System 5.1 SP1 Administrator"s Guide (5900-1499, April 2011)
When inode information is no longer dependable, the kernel marks it bad in
memory. This is followed by a message to mark it bad on disk as well unless the
mount command ioerror option is set to disable, or there is subsequent I/O failure
when updating the inode on disk. No further operations can be performed on the
inode.
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. The
file system can be remounted without a full fsck unless the VX_FULLFSCK flag is
set for the file system.
V-2-19
WARNING: msgcnt x: mesg 019: V-2-19: vx_log_add - mount_point file system log
overflow
Description:
Log ID overflow. When the log ID reaches VX_MAXLOGID (approximately one billion
by default), a flag is set so the file system resets the log ID at the next opportunity.
If the log ID has not been reset, when the log ID reaches VX_DISLOGID
(approximately VX_MAXLOGID plus 500 million by default), the file system is
disabled. Since a log reset will occur at the next 60 second sync interval, this
should never happen.
Recommended action:
Unmount the file system and use fsck to run a full structural check.
Diagnostic messages
Dewey kernel messages
198