Skip to main content
NetApp Knowledge Base

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

Last Updated:

Applies to

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


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 was still bound to X handles 
and cannot be deleted.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.