HP JFS 3.3 and HP OnLineJFS 3.3 VERITAS File System 3.3 System Administrator's Guide

Appendix A 139
Kernel Messages
Kernel Messages
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 and use fsck to run a full
structural check.
Message 019 WARNING: msgcnt x : vxfs: mesg 019: vx_log_add -
mount_point file system log overflow
• Explanation
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.
Message 020 WARNING: msgcnt x : vxfs: mesg 020: vx_logerr -
mount_point file system log error errno
• Explanation
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.
Message 021 WARNING: msgcnt x : vxfs: mesg 021: vx_fs_init -
mount_point file system
validation failure
• Explanation
When a VxFS file system is mounted, the structure is read from disk.
If the file system ismarked clean, the structure is correct and the first
block of the intent log is cleared.
If there is any I/O problem or the structure is inconsistent, the kernel