HP JFS 3.3 and HP OnLineJFS 3.3 VERITAS File System 3.3 System Administrator's Guide

134 AppendixA
Kernel Messages
Kernel Messages
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.
• 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.
Message 010 WARNING: msgcnt x : vxfs: mesg 010: vx_ialloc -
mount_point file system inode inumber not free
• Explanation
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.
• Action
Unmount the file system and use fsck to run a full structural check.
Message 011 NOTICE: msgcnt x : vxfs: mesg 011: vx_noinode -
mount_point file system out of inodes
• Explanation
The file system is out of inodes.
• Action
Monitor the free inodes in the file system. If the file system is getting
full, create more inodes either by removing files or by expanding the
file system. File system resizing is described in “Online System
Administration” in Chapter 1 , “The VxFS File System” and in
fsadm_vxfs(1M).
Message 012 WARNING: msgcnt x : vxfs: mesg 012: vx_iget - mount_point
file system invalid inode number inumber