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

Recommended action:
Check the console log for I/O errors. If the problem was caused by a disk failure,
replace the disk before the file system is mounted for write access, and use fsck
to run a full structural check.
V-2-7
WARNING: msgcnt x: mesg 007: V-2-7: vx_sumupd - mount_point file system
summary update in inode au iaun failed
Description:
An I/O error occurred while writing the allocation unit or inode allocation unit
bitmap summary to disk. This sets the VX_FULLFSCK flag on the file system. If the
VX_FULLFSCK flag cannot be set, the file system is disabled.
Recommended action:
Check the console log for I/O errors. If the problem was caused by a disk failure,
replace the disk before the file system is mounted for write access, and use fsck
to run a full structural check.
V-2-8
WARNING: msgcnt x: mesg 008: V-2-8: vx_direrr: function - mount_point file
system dir inode dir_inumber dev/block device_ID/block dirent inode
dirent_inumber error errno
Description:
A directory operation failed in an unexpected manner. The mount point, inode,
and block number identify the failing directory. If the inode is an immediate
directory, the directory entries are stored in the inode, so no block number is
reported. If the error is ENOENT or ENOTDIR, an inconsistency was detected in the
directory block. This inconsistency could be a bad free count, a corrupted hash
chain, or any similar directory structure error. If the error is EIO or ENXIO, an I/O
failure occurred while reading or writing the disk block.
The VX_FULLFSCK flag is set in the super-block so that 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 was caused by a disk failure,
replace the disk before the file system is mounted for write access. Unmount the
file system and use fsck to run a full structural check.
Diagnostic messages
Dewey kernel messages
192