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

HP-UX Handbook – Rev 13.00 Page 27 (of 47)
Chapter 14 Journaled File System (JFS)
October 29, 2013
the bitmap, the file system has been corrupted. This may have occurred because a user or process
wrote directly to the device or used fsdb to change the file system. The VX_FULLFSCK flag is
set. If the map that failed was a free extent bitmap, and the VX_FULLFSCK flag can't be set,
then the file system is disabled.
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 was writing to the device, report the problem to your customer support organization.
Unmount the file system and use fsck to run a full structural check.
Message: 006, 007
WARNING: msgcnt x: vxfs: mesg 006: vx_sumupd -mount_point file system summary
update in au aun failed
WARNING: msgcnt x: vxfs: mesg 007: vx_sumupd - mount_point file system summary
update in inode au iaun failed
Explanation:
An I/O error occurred while writing the allocation unit or inode allocation unit bitmap summary
to disk. This sets the VX_FULLFSCK flag on the file system. If the VX_FULLFSCK flag can't
be set, the file system is disabled.
Action: Check the console log for I/O errors. If the problem was caused by a disk failure, replace
the disk before the file system is mounted for write access, and use fsck to run a full structural
check.
Message: 008, 009
WARNING: msgcnt x: vxfs: mesg 008: vx_direrr - mount_point file system inode
inumber block blkno error errno
WARNING: msgcnt x: vxfs: mesg 009: vx_direrr - mount_point file system inode
inumber immediate directory error errno
Explanation:
A directory operation failed in an unexpected manner. The mount point,inode, and block number
identify the failing directory. If the inode is an immediate directory, the directory entries are
stored in the inode, so no block number is reported. If the error is ENOENT or ENOTDIR, an
inconsistency was detected in the directory block. This inconsistency could be a bad free count, a
corrupted hash chain, or any similar directory structure error. If the error is EIO or ENXIO, an
I/O failure occurred while reading or writing the disk block. The VX_FULLFSCK flag is set in
the super-block so that 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 was caused by a disk failure,
replace the disk before the file system is mounted for write access. Unmount the file system and
use fsck to run a full structural check.
Message: 010
WARNING: msgcnt x: vxfs: mesg 010: vx_ialloc - mount_point file system inode