Veritas File System 5.1 SP1 Administrator"s Guide (5900-1499, April 2011)

Description:
An attempt to write the file system super block failed due to a disk I/O error. If
the file system was being mounted at the time, the mount will fail. If the file system
was mounted at the time and the full fsck flag was being set, the file system will
probably be disabled and Message 031 will also be printed. If the super-block was
being written as a result of a sync operation, no other action is taken.
Recommended action:
Resolve the condition causing the disk error. If the error was the result of a
temporary condition (such as accidentally turning off a disk or a loose cable),
correct the condition. Check for loose cables, etc. Unmount the file system and
use fsck to run a full structural check.
If an actual disk error occurred, make a backup of the file system, replace or
reformat the disk drive, and restore the file system from backups. Consult the
documentation specific to your system for information on how to recover from
disk errors. The disk driver should have printed a message that may provide more
information.
V-2-56
WARNING: msgcnt x: mesg 056: V-2-56: vx_mapbad - mount_point file system
extent allocation unit state bitmap number number 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 VX_FULLFSCK flag cannot be set, the file system
is disabled.
Recommended 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.
207Diagnostic messages
Dewey kernel messages