VERITAS File System 4.1 Administrator's Guide

Kernel Messages
Kernel Messages
Appendix B216
017 • 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 is writing to the
device, report the problem to your customer support organization. In
either case, unmount the file system. The file system can be remounted
without a full fsck unless the VX_FULLFSCK flag is set for the file
system.
019 WARNING: msgcnt x: mesg 019: V-2-19: vx_log_add - mount_point file
system log overflow
• Description
Log ID overflow. When the log ID reaches VX_MAXLOGID
(approximately one billion by default), a flag is set so the file system
resets the log ID at the next opportunity. If the log ID has not been reset,
when the log ID reaches VX_DISLOGID (approximately VX_MAXLOGID
plus 500 million by default), the file system is disabled. Since a log reset
will occur at the next 60 second sync interval, this should never happen.
• Action
Unmount the file system and use fsck to run a full structural check.
020 WARNING: msgcnt x: mesg 020: V-2-20: vx_logerr - mount_point file
system log error errno
• Description
Intent log failed. The kernel will try to set the VX_FULLFSCK and
VX_LOGBAD flags in the super-block to prevent running a log replay. If
the super-block can’t be updated, the file system is disabled.
• Action
Unmount the file system and use fsck to run a full structural check.
Check the console log for I/O errors. If the disk failed, replace it before
remounting the file system.
Table B-1 (Continued)
Message
Number
Message and Definition