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

HP-UX Handbook – Rev 13.00 Page 39 (of 47)
Chapter 14 Journaled File System (JFS)
October 29, 2013
Message: 048
WARNING: msgcnt x: vxfs: mesg 048: vx_mapbad - mount_point file system extent
allocation unit state bitmap number marked bad
Explanation:
If there is an I/O failure while writing a bitmap, the map is marked bad. The kernel considers the
maps to be invalid, so does not do any more resource allocation from maps. This situation can
cause the file system to report "out of space" or "out of inode" error messages even though df
may report an adequate amount of free space. This error may also occur due to bitmap
inconsistencies. If a bitmap fails a consistency check, or blocks are freed that are already free in
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 VX_FULLFSCK flag can't be set, 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: 049
WARNING: msgcnt x: vxfs: mesg 049: vx_esum_bad - mount_point file system extent
allocation unit summary number marked bad
Explanation:
An I/O error occurred reading or writing an extent allocation unit summary. The
VX_FULLFSCK flag is set. 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 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: 050
WARNING: msgcnt x: vxfs: mesg 050: vx_isum_bad - mount_point file system inode
allocation unit summary number marked bad
Explanation: An I/O error occurred reading or writing an inode allocation unit summary. The
VX_FULLFSCK flag is set. 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 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.