Skip to main content
NetApp Knowledge Base

Creation of Snapshots fails due to clone backed by Snapshot

  1. Last updated
    Oct 7, 2024
  2. Save as PDF
Views:
2,113
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:
10/7/2024, 4:54:51 PM

Applies to

  • ONTAP 9
  • SIS File Clone
  • SIS Clone

Issue

  • Snapshot creating operations fails:

::> snapshot create -vserver MySVM -volume MyVolume -snapshot MySnapshot
Error: command failed: Failed to create snapshot "MySnapshot" of volume "MyVolume" on Vserver "MySVM". Reason: Snapshot operation not allowed due to clones backed by snapshots. Try again after sometime.

  • Event log shows:

::> event log show
Wed Nov 08 15:10:00 +0100 [MyCluster-01: snapd_cmode: wafl.snap.create.skip.reason:error]: MyVolume  655ccab3-a41b-11e5-848b-000e1e245750: Skipping creation of MySnapshot Snapshot copy (Snapshot operation not allowed due to clones backed by snapshots. Try again after sometime.).

  • The volume that fails to create snapshots has a busy=true Snapshot, owned by SIS Clone:

::> snapshot show -busy true -fields busy,owner,create-time
vserver         volume      snapshot                create-time              busy owners
--------------- ----------- ----------------------- ------------------------ ---- -----------
MySVM           MyVolume    SomeSnapshot            Wed Nov 01 06:00:00 2023 true "SIS Clone"

  • The associated SIS File clone split operation shows Split Load but seems stuck and not progressing:

::> volume file clone split load show
Node                            Max        Current    Token         Allowable
                                Split Load Split Load Reserved Load Split Load
------------------------------- ---------- ---------- ------------- ----------
MyCluster-01                     675TB         0B            0B     675TB
MyCluster-02                     675TB        1MB            0B     675.0TB
2 entries were displayed.

 

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.