Skip to main content
NetApp Knowledge Base

Unable to delete old root volumes after root volume migration

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

Applies to

ONTAP 9

Issue

  • After performing root volume migration, the old root volumes tagged to node vserver are still seen in the list:

Example: 

Cluster::> vol show -vserver node-01
Vserver   Volume       Aggregate    State      Type       Size  Available Used%
--------- ------------ ------------ ---------- ---- ---------- ---------- -----
node-01   TEMPROOT         -           -        RW          -          -      -
node-01   node01_root      -           -        RW          -          -      -
node-01   new_root    node01_root     online    RW    348.6GB    272.2GB    17%
3 entries were displayed.

  • From the above example, the root volume currently active is "new_root" and the remaining volumes shown are old ones, which can be removed. However, deletion of these volumes fails, as they are stale entries and have no vservers tagged to them.

 

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.