Skip to main content
NetApp Knowledge Base

CONTAP-507227: Volume fenced for protocol access due to "Volume is busy"

  1. Last updated
  2. Save as PDF
Views:
9
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Issue

  • Access fenced for protocol access
  • Fencing caused by "coordinated_snaprestore":

 
::> volume show -volume fg -fields is-protocol-access-fenced, protocol-access-fenced-by
vserver volume is-protocol-access-fenced protocol-access-fenced-by
------- ------ ------------------------- -------------------------
svm1 fg true coordinated_snaprestore
svm1 fg__0001 true coordinated_snaprestore
svm1 fg__0002 true coordinated_snaprestore
svm1 fg__0003 true coordinated_snaprestore
 
 
  • Volume, qtree or snapshot cannot be deleted on this volume

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.