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

Appendix A 135
Kernel Messages
Kernel Messages
• Explanation
When the kernel tries to read an inode, it checks the inode number
against the valid range. If the inode number is out of range, the data
structure that referenced the inode number is incorrect and must be
fixed.
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 013 WARNING: msgcnt x : vxfs: mesg 013: vx_iposition -
mount_point file system inode inumber invalid inode list
extent
• Explanation
For a Version 2 and above disk layout, the inode list is dynamically
allocated. When the kernel tries to read an inode, it must look up the
location of the inode in the inode list file. If the kernel finds a bad
extent, the inode can’t be accessed. All of the inode list extents are
validated when the file system is mounted, so if the kernel finds a bad
extent, the integrity of the inode list is questionable. This is a very
serious error.
The VX_FULLFSCK flag is set in the super-block and the file system is
disabled.
• Action
Unmount the file system and use fsck to run a full structural check.
Message 014 WARNING: msgcnt x : vxfs: mesg 014: vx_iget - inode table
overflow
• Explanation
All the system in-memory inodes are busy and an attempt was made
to use a new inode.
• Action
Look at the processes that are running and determine which
processes are using inodes. If it appears there are runaway processes,
they might be tying up the inodes. If the system load appears normal,
increase the vx_ninode parameter in the kernel (see “Internal Inode