Veritas File System 5.0 Administrator's Guide (September 2006)

Table B-1
Kernel messages (continued)
Message and DefinitionMessage Number
WARNING: msgcnt x: mesg 002: V-2-2: vx_snap_strategy -
mount_point file system write attempt to read-only file system
WARNING: msgcnt x: mesg 002: V-2-2: vx_snap_copyblk -
mount_point file system write attempt to read-only file system
■ Description
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.
002
WARNING: msgcnt x: mesg 003: V-2-3: vx_mapbad - mount_point
file system free extent bitmap in au aun marked bad
WARNING: msgcnt x: mesg 004: V-2-4: vx_mapbad - mount_point
file system free inode bitmap in au aun marked bad
WARNING: msgcnt x: mesg 005: V-2-5: vx_mapbad - mount_point
file system inode extended operation bitmap in au aun marked bad
■ Description
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 map that failed was a free
extent bitmap, and the VX_FULLFSCK flag cannot 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.
003, 004, 005
Diagnostic messages
Kernel messages
228