Volume clone split failed due to volume containing locked snapshots
Applies to
- ONTAP 9
- All FAS Platforms
Issue
- Can not split the clone volume from the parent.
- From the EMS log, the volume has locked snapshots and is not splitting.
Example:
[nodename: vv_config_worker10: wafl.vv.clone.splitBusySnap:notice]: Volume 'volname@vserver:41b77ac1-7cc7-11e7-a8d2-00a098ad7381' has locked snapshots, not splitting.
[nodename: vv_config_worker10: wafl.config.req.error:debug]: Config request 'VV_CONFIG_REQ_CLONE_SPLIT_START' by WAFL for volume volname 41b77ac1-7cc7-11e7-a8d2-00a098ad7381 is not being processed because of the error: '387 - CR_VV_VOLUME_SNAPSHOTS'.
[nodename mgwd: mgmtgwd.jobmgr.jobcomplete.failure:info]: Job "Clone Split" [id 14119] (Split volname) completed unsuccessfully: Volume has locked snapshots (1).
- The clone volume has a base snapmirror snapshot on the source site.
Example:
::> volume snapshot show -vserver <vserver> -volume <volume> -fields owners,dependency
vserver volume snapshot owners dependency
------- ------ ---------------------------------------------------------------------------- ------ ----------
svm1 vol1_clone snapmirror.c4316d88-1e20-11ed-9f0c-005056a0d690_2159800773.2023-04-17_104625 - snapmirror