Skip to main content
NetApp Knowledge Base

TMP volume remains after failed vol move due to WAFL inconsistency

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

Applies to

  • ONTAP 9
  • Volume Move

Issue

During volume move operation, the ONTAP system experienced a WAFL inconsistency panic. This resulted in the move being stopped which left behind a TMP volume.
Teams are unable to delete the TMP volume:
 
Standard volume operations fail:
 

::*> volume offline -vserver svm1 -volume temp_261351358fg_oss_17xxxx6606_0014 -force true

Warning: Forcing offline volume temp_261351358fg_oss_17xxxx6606_0014 in Vserver ipp_oma1-s3-local can potentially disrupt access to files in other volumes.
Do you want to continue? {y|n}: y
Volume "svm1:temp_261351358fg_oss_17xxxx6606_0014" is now offline.

::*> volume delete -vserver ipp_oma1-s3-local -volume temp_261351358fg_oss_17xxxx6606_0014

Error: command failed: Cannot delete object store volume "temp_261351358fg_oss_17xxxx6606_0014" in Vserver "svm1", because this volume is associated with object store bucket "bucket1".

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.