VERITAS File System 4.1 Administrator's Guide

Kernel Messages
Kernel Messages
Appendix B 215
017 WARNING: msgcnt x: mesg 017: V-2-17: vx_stablestore - mount_point
file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_tranitimes - mount_point
file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_trunc - mount_point file
system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_write_alloc2 - mount_point
file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_write_default -
mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_zero_alloc - mount_point
file system inode inumber marked bad in core
• Description
When inode information is no longer dependable, the kernel marks it bad
in memory. This is followed by a message to mark it bad on disk as well
unless the mount command ioerror option is set to disable, or there is
subsequent I/O failure when updating the inode on disk. No further
operations can be performed on the inode.
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 errormessage 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.
Table B-1 (Continued)
Message
Number
Message and Definition