topic Re: Unable to delete cloned volume in ONTAP Discussions

Unable to delete cloned volume

lsran007 — Thu, 27 Oct 2022 18:58:03 GMT

I have snapmirrorred volume from onprem (Ontap) to fsxn instance in AWS (Ontap) and created a clone on destination (fsxn filesystem) and is unable to delete the clone volume.

There is no active snapshot for the clone volume.

Error: command failed: Volume "clone_xxx" in Vserver "use1-fsxn-svm-xxx" is the destination or source endpoint of one or more SnapMirror relationships. Before you can delete the volume, you must delete the relationships for
which it is the destination endpoint, and release the source information for the relationships for which it is the source endpoint using "snapmirror release".

Have anyone experienced this?

Re: Unable to delete cloned volume

Ontapforrum — Fri, 28 Oct 2022 08:59:15 GMT

What is the output of this command:
::> snapmirror list-destinations -instance

https://kb.netapp.com/Advice_and_Troubleshooting/Data_Protection_and_Security/SnapMirror/Unable_to_delete_a_volume_as_it_is_the_source_endpoint_of_one_or_more_SnapMirror_relationships

Re: Unable to delete cloned volume

lsran007 — Fri, 28 Oct 2022 17:39:27 GMT

snapmirror list-destinations doesn't show up any dependency for cloned volume.

I ran a similar test keeping CVO instance as destination and it works as expected. I feel there is something special for fsxn filesystem served as managed service.

Re: Unable to delete cloned volume

Ontapforrum — Sun, 30 Oct 2022 12:58:28 GMT

Have you tried to delete it vi AWS Console/CLI ?

SnapMirror volumes must be deleted using the AWS Management Console or CLI.

https://docs.netapp.com/us-en/cloud-manager-fsx-ontap/use/task-manage-fsx-volumes.html#manage-snapshot-copies

If that doesn't help. Clue is also given here: Section- SVM or volume deletion
https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/cannot-delete-svm.html

Re: Unable to delete cloned volume

chenguanghui — Fri, 22 Nov 2024 03:19:40 GMT

hello:

If you report an error, you can see that the parent volume of the clone volume you want to delete has a snapmirror relationship, in which case you must delete the snapmirror relationship first and then delete the volume that you don't want

i hope to help you