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

Appendix A 133
Kernel Messages
Kernel Messages
the bitmap, the file system has been corrupted. This may have
occurred because a user or process wrote directly to the device or used
fsdb to change the file system.
The VX_FULLFSCK flag is set. If the map that failed was a free extent
bitmap, and the VX_FULLFSCK flag can’t be set, then the file system is
disabled.
• Action
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk. If the problem is not related to an I/O failure, find
out how the disk became corrupted. If no user or process was writing
to the device, report the problem to your customer support
organization. Unmount the file system and use fsck to run a full
structural check.
Message 006, 007 WARNING: msgcnt x : vxfs: mesg 006: vx_sumupd -
mount_point file system summary update in au aun failed
WARNING: msgcnt x : vxfs: mesg 007: vx_sumupd -
mount_point file system summary update in inode au iaun
failed
• Explanation
An I/O error occurred while writing the allocation unit or inode
allocation unit bitmap summary to disk. This sets the VX_FULLFSCK
flag on the file system. If the VX_FULLFSCK flag can’t be set, the file
system is disabled.
• 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, and use fsck to run a full structural check.
Message 008, 009 WARNING: msgcnt x : vxfs: mesg 008: vx_direrr: caller_id
- mount_point file system inode inumber block blkno
error errno
WARNING: msgcnt x : vxfs: mesg 009: vx_direrr: caller_id
- mount_point file system inode inumber immediate
directory error errno
• Explanation
A directory operation failed in an unexpected manner. caller_id
identifies the routine that generated the message. The mount point,
inode, and block number identify the failing directory. If the inode is