VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Kernel Warning Messages
40 VERITAS Volume Manager Troubleshooting Guide
vxvm:vxio:WARNING: check_ilocks: overlapping ilocks: offset for length,
offset for length
vxvm:vxio:WARNING: check_ilocks: stranded ilock on object_name start
offset len length
◆ Description: These internal errors do not occur unless there is a bug in VxVM.
◆ Action: Contact Customer Support.
vxvm:vxio:WARNING: detaching RAID-5 volume
◆ Description: Eithera double-failure conditionin the RAID-5 volumehas been detected
in the kernel or some other fatal error is preventing further use of the array.
◆ Action: If twoor more disks havebeen lostdue to a controller or power failure, usethe
vxrecover utility to recover them once they have been re-attached to the system.
Check for other console error messages that may provide additional information
about the failure.
vxvm:vxio:WARNING: Device major, minor: Received spurious close
◆ Description: A close was received for an object that was not open. This can only
happen if the operating system is not correctly tracking opens and closes.
◆ Action: No action is necessary; the system will continue.
vxvm:vxio:WARNING: Double failure condition detected on RAID-5 volume
◆ Description: I/O errors have been received in more than one column of a RAID-5
volume. This could be caused by:
- a controller failure making more than a single drive unavailable
- the loss of a second drive while running in degraded mode
- two separate disk drives failing simultaneously (unlikely)
◆ Action: Correct the hardware failures if possible. Then recover the volume using the
vxrecover command.
vxvm:vxio:WARNING: DRL volume volume is detached
◆ Description: A Dirty Region Logging volume became detached because a DRL log
entry could notbe written.If thisis due toa mediafailure,other errorsmay havebeen
logged to the console.
◆ Action: The volume containing the DRL log continues in operation. If the system fails
before the DRL has been repaired, a full recovery of the volume’s contents may be
necessary and will be performed automatically when the system is restarted. To
recover from this error, use the vxassist addlog command add a new DRL log to
the volume.