HP-UX HB v13.00 Ch-14 - JFS

HP-UX Handbook – Rev 13.00 Page 28 (of 47)
Chapter 14 Journaled File System (JFS)
October 29, 2013
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. .
Message: 012
WARNING: msgcnt x: vxfs: mesg 012: vx_iget - mount_point file system invalid inode
number inumber
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: This is a very serious error.
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. 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.