Error 80000011 is logged by vxio

Article: 100019570
Last Published: 2022-01-27
Ratings: 0 0
Product(s): InfoScale & Storage Foundation

Problem

Error 80000011 is logged by vxio

 

 

Error Message

vxio: Disk driver returned error 80000011 when vxio tried to read block xx on HarddiskX

 

 

Solution

This message is for informational purposes and can safely be ignored under the following conditions.

The Disk Group has just been deported on the node the vxio errors are reported, and the disks involved, detailed in the above messages by "HarddiskX" are all from that DiskGroup.  The disk groups deport message will appear in the Window Application Event log just before the vxio messages appear in the Windows SystemEvent Log

INFORMATION   10232(0xe51527f8)   VxSvc_vxvm <sourceserver>              
Deported cluster dynamic disk group <disk group name>.

The vxio messages will stop being logged on the target cluster group failover node when the following even tis logged to show the Disk Group is imported

INFORMATION  10226(0x651527f2) VxSvc_vxvm <targetserver>              
Imported cluster dynamic disk group <disk group name> to cluster dynamic disk group<disk group name>

What is Happening?

While the DiskGroup is being deported, and then imported on a new node, there is a rescan initiated on the source server.  During the rescan the source server will still try to rescan the disks until the Disk Group object is no longer present on that server.  
 
The error 80000011 means "device busy" and in this case is indicating that the disks are under reservation of another server.

In this circumstance the message is expected and can be ignored.  They will stop once the Disk Group objects are removed from the source server.

IMPORTANT NOTE

In situations other than the one explained above, this message may indicate a hardware problem.  
 
If an active cluster node receives this message on an imported cluster Disk Group, it indicates it has lost control of the disks and its likely an application fault will follow.  
 
This would need troubleshooting of the circumstances by investigating devices and path infrastructure between the server and the storage array, including the physical hard disks that make up the LUN.


 
 

 

Was this content helpful?