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

V-2-9
WARNING: msgcnt x: mesg 009: V-2-9: vx_direrr: function - mount_point file
system dir inode dir_inumber dirent inode dirent_inumber immediate directory
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.
V-2-10
WARNING: msgcnt x: mesg 010: V-2-10: vx_ialloc - mount_point file system inode
inumber not free
Description:
When the kernel allocates an inode from the free inode bitmap, it checks the mode
and link count of the inode. If either is non-zero, the free inode bitmap or the
inode list is corrupted.
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:
Unmount the file system and use fsck to run a full structural check.
V-2-11
NOTICE: msgcnt x: mesg 011: V-2-11: vx_noinode - mount_point file system out
of inodes
Description:
193Diagnostic messages
Dewey kernel messages