HP JFS 3.3 and HP OnLineJFS 3.3 VERITAS File System 3.3 System Administrator's Guide
138 AppendixA
Kernel Messages
Kernel Messages
WARNING: msgcnt
x
: vxfs: mesg 017: vx_logwrite_flush -
mount_point
file system inode
inumber
marked bad
WARNING: msgcnt
x
: vxfs: mesg 017: vx_oltmount_iget -
mount_point
file system inode
inumber
marked bad
WARNING: msgcnt
x
: vxfs: mesg 017: vx_overlay_bmap -
mount_point
file system inode
inumber
marked bad
WARNING: msgcnt
x
: vxfs: mesg 017: vx_readnomap -
mount_point
file system inode
inumber
marked bad
WARNING: msgcnt
x
: vxfs: mesg 017: vx_reorg_trunc -
mount_point
file system inode
inumber
marked bad
WARNING: msgcnt
x
: vxfs: mesg 017: vx_stablestore -
mount_point
file system inode
inumber
marked bad
WARNING: msgcnt
x
: vxfs: mesg 017: vx_tranitimes -
mount_point
file system inode
inumber
marked bad
WARNING: msgcnt
x
: vxfs: mesg 017: vx_trunc -
mount_point
file system inode
inumber
marked bad
WARNING: msgcnt
x
: vxfs: mesg 017: vx_write_alloc2 -
mount_point
file system inode
inumber
marked bad
WARNING: msgcnt
x
: vxfs: mesg 017: vx_write_default -
mount_point
file system inode
inumber
marked bad
WARNING: msgcnt
x
: vxfs: mesg 017: vx_zero_alloc -
mount_point
file system inode
inumber
marked bad
• Explanation
When inode information is no longer dependable, the kernel marks it
bad on disk. The most common reason for marking an inode bad is a
disk I/O failure. If there is an I/O failure in the inode list, on a
directory block, or an indirect address extent, the integrity of the data
in the inode, or the data the kernel tried to write to the inode list, is
questionable. In these cases, the disk driver prints an error message
and one or more inodes are marked bad.
The kernel also marks an inode bad if it finds a bad extent address,
invalid inode fields, or corruption in directory data blocks during a
validation check. A validation check failure indicates the file system
has been corrupted. This usually occurs because a user or process has
written directly to the device or used fsdb to change the file system.
The VX_FULLFSCK flag is set in the super-block so 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 is a disk failure,