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

Description:
All the system in-memory inodes are busy and an attempt was made to use a new
inode.
Recommended 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 “Tuning the VxFS file system” on page 45.
V-2-15
WARNING: msgcnt x: mesg 015: V-2-15: vx_ibadinactive - mount_point file system
cannot mark inode inumber bad
WARNING: msgcnt x: mesg 015: V-2-15: vx_ilisterr - mount_point file system
cannot mark inode inumber bad
Description:
An attempt to mark an inode bad on disk, and the super-block update to set the
VX_FULLFSCK flag, failed. This indicates that a catastrophic disk error may have
occurred since both an inode list block and the super-block had I/O failures. The
file system is disabled to preserve file system integrity.
Recommended action:
Unmount the file system and use fsck to run a full structural check. Check the
console log for I/O errors. If the disk failed, replace it before remounting the file
system.
V-2-16
WARNING: msgcnt x: mesg 016: V-2-16: vx_ilisterr - mount_point file system error
reading inode inumber
Description:
An I/O error occurred while reading the inode list. The VX_FULLFSCK flag is set.
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.
195Diagnostic messages
Dewey kernel messages