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

150 AppendixA
Kernel Messages
Kernel Messages
To maintain reliable usage counts, VxFS maintains the user and
group quotas files as structural files in the structural fileset. These
files are updated as part of the transactions that allocate and free
blocks and inodes. For compatibility with the quota administration
utilities, VxFS also supports the standard user visible quota files.
When quotas are turned off, synced, or new limits are added, VxFS
tries to update the external quota files. When quotas are enabled,
VxFS tries to read the quota limits from the external quotas file. If
these reads or writes fail, the external quotas file is out of date.
• Action
Determine the reason for the failure on the external quotas file and
correct it. Recreate the quotas file.
Message 050, 051,
052, 053, 054, 055
• These messages do not apply to HP-UX systems.
Message 056 WARNING: msgcnt x : vxfs: mesg 056: vx_mapbad -
mount_point file system extent allocation unit state
bitmap number 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