VERITAS File SystemÖ 3.5 (HP OnlineJFS/JFS3.5) AdministratorÆs Guide (December 2002)

Appendix B
Kernel Messages
Kernel Messages
126
035 WARNING: msgcnt
x : vxfs: mesg 035: vx_inactive - mount_point file system inactive of
locked inode inumber
• Description
VOP_INACTIVE was called for an inode while the inode was being used. This should never
happen, but if it does, the file system is disabled.
•Action
Unmount the file system and use fsck to run a full structural check. Report as a bug to
your customer support organization.
036 WARNING: msgcnt
x : vxfs: mesg 036: vx_lctbad - mount_point file system link count
table
lctnumber bad
• Description
Update to the link count table (LCT) failed.
For a Version 2 and above disk layout, the LCT contains the link count for all the
structural inodes. The VX_FULLFSCK flag is set in the super-block. If the super-block can’t
be written, the file system is disabled.
•Action
Unmount the file system and use fsck to run a full structural check.
037 WARNING: msgcnt
x : vxfs: mesg 037: vx_metaioerr - file system meta data error
• Description
A read or a write error occurred while accessing file system metadata. The full fsck flag
on the file system was set. The message specifies whether the disk I/O that failed was a
read or a write.
File system metadata includes inodes, directory blocks, and the file system log. If the error
was a write error, it is likely that some data was lost. This message should be accompanied
by another file system message describing the particular file system metadata affected, as
well as a message from the disk driver containing information about the disk I/O error.
•Action
Resolve the condition causing the disk error. If the error was the result of a temporary
condition (such as accidentally turning off a disk or a loose cable), correct the condition.
Check for loose cables, etc. Unmount the file system and use fsck to run a full structural
check (possibly with loss of data).
In case of an actual disk error, if it was a read error and the disk driver remaps bad sectors
on write, it may be fixed when fsck is run since fsck is likely to rewrite the sector with
the read error. In other cases, you replace or reformat the disk drive and restore the file
system from backups. Consult the documentation specific to your system for information
on how to recover from disk errors. The disk driver should have printed a message that
may provide more information.
Message
Number
Message and Definition