VERITAS File System 3.5 (HP OnlineJFS/JFS 3.5) Administrator's Guide (August 2003)

Appendix B
Kernel Messages
Kernel Messages
95
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 aun failed
• Description
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.
008, 009 WARNING: msgcnt x : vxfs: mesg 008: vx_direrr - mount_point file system inode inumber
block blkno error errno
WARNING: msgcnt x : vxfs: mesg 009: vx_direrr - mount_point file system inode inumber
immediate directory error errno
• Description
A directory operation failed in an unexpected manner. The mount point, inode, and block
number identify the failing directory. If the inode is 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.
010 WARNING: msgcnt x : vxfs: mesg 010: vx_ialloc - mount_point file system inode inumber
not free
• Description
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
Number
Message and Definition