Clone split failure and state mismatch
Applies to
- ONTAP 9
- Azure NetApp Files/Cloud Volumes Service (CVS)
- AFF/FAS/ASA
Issue
- Clone split operations failed on multiple volumes in an ONTAP cluster using Cloud Volumes Service (CVS).
- After the failure, CVS continued to show the affected volumes in a persistent ‘clonesplit in progress’ state, even though ONTAP reported no active splits.
- This mismatch blocked volume revert and delete operations for several days.
- Log Output (example):
[Node-1: wafl_exempt03: wafl.scan.clone.split.abort:info]: Volume vol_1, clone split operation stopped.[Node-1: wafl_exempt14: wafl.scan.clone.split.abort:info]: Volume vol_2, clone split operation stopped.[Node-1: wafl_exempt12: wafl.scan.clone.split.abort:info]: Volume vol_3, clone split operation stopped.
- Attempts to revert or delete affected volumes failed with errors such as:
- Cannot revert a Volume while a Clone Split is in progress.
- Cannot delete volume because clone volumes are still copying data.
- HTTP 409 API errors
