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

132 AppendixA
Kernel Messages
Kernel Messages
becoming full. If a runaway process has used up all the space, stop
that process, find the files created by the process, and remove them. If
the file system is out of space, remove files, defragment, or expand the
file system.
To remove files, use the find command to locate the files that are to
be removed. To get the most space with the least amount of work,
remove large files or file trees that are no longer needed. To
defragment or expand the file system, use fsadm_vxfs(1M).
Message 002 WARNING: msgcnt x: vxfs: mesg 002: vx_snap_strategy -
mount_point file system write attempt to read-only file
system
WARNING: msgcnt x: vxfs: mesg 002: vx_snap_copyblk -
mount_point file system write attempt to read-only file
system
• Explanation
The kernel tried to write to a read-only file system. This is an unlikely
problem, but if it occurs, the file system is disabled.
• Action
The file system was not written, so no action is required. Report this
as a bug to your customer support organization.
Message 003, 004,
005
WARNING: msgcnt x: vxfs: mesg 003: vx_mapbad -
mount_point file system free extent bitmap in au aun
marked bad
WARNING: msgcnt x: vxfs: mesg 004: vx_mapbad -
mount_point file system free inode bitmap in au aun
marked bad
WARNING: msgcnt x: vxfs: mesg 005: vx_mapbad -
mount_point file system inode extended operation bitmap
in au aun 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