Skip to main content
NetApp Knowledge Base

vVOL VMDK deletion fails with error "volume of naa.xyz was still bound to X handles and cannot be deleted."

Views:
20
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

Applies to

  • vSphere APIs for Storage Awareness (VASA)
  • Virtual Volumes (vVOL)

Issue

When in use vVOL VMDK's are bound to a host. Under certain circumstances it is possible that the host never releases the active binds, for example, if the host fails due to a hardware error. In this case a deletion of the vVOL VMDK will fail with error: 
FINAL FAILURE deleteVirtualVolume, error (RESOURCE_BUSY / Caused by: volume of naa.xyz was still bound to X handles 
and cannot be deleted.
Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support