HP-UX HB v13.00 Ch-14 - JFS

HP-UX Handbook – Rev 13.00 Page 31 (of 47)
Chapter 14 Journaled File System (JFS)
October 29, 2013
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, 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: 018
WARNING: msgcnt x: vxfs: mesg 018: vx_idelxwri_done - <mount_point> file system
inode <inumber> had a write error at offset <off>
Explanation:
This message prints when the file system encounters an error while flushing non-synchronous
extending write data. Since the data for the file couldn't be written, the file probably contains
stale data. If the file system was mounted with the blkclear mount option, then the
VX_AF_NOGROW flag is set on the file. When this flag is set, further attempts to extend the
file fail. The flag is cleared when the file is truncated.
Action: Check the console log for I/O errors. If the problem was caused by a disk failure, then
the disk should be fixed as soon as possible. If the disk has failed, it should be repaired before
the file system is mounted for write access. Make sure the fsck program does a full structural
check at the next administrative period.
The ff utility should be used to determine the name of the file that failed. The contents of the file
should be checked, and if necessary restored from backup or recreated.