SIS Clone operation failed to start with error Max Dense Limit is reached
Applies to
- ONTAP
- Deduplication
- SIS Clones
Issue
- Creating VM clones on the host end are delayed than usual.
- When attempting a SIS clone operation on a file or LUN level, the following error is reported:
cluster1::> volume file clone create -volume vol1 -source-path /myfile -destination-path /myfile_copy Error: command failed: Clone start failed: Clone operation failed to start: Max Dense limit is reached. cluster1::>
- And the following EMS entry is triggered:
Fri Apr 17 21:26:25 CEST [cluster1-01: wafl_exempt17: sis.max.saving.near:notice]: Maximum savings limit nearly reached on volume vol1@vserver:571fe7af-29ea-11d3-adbf-123578563412. Mon Apr 20 05:17:40 CEST [cluster1-01: svc_queue_thread: wafl.sis.clone.create.failed:info]: File clone create of file /vol/vol1q1/mydata.vmdk in volume vol1 failed with error: Max Dense limit is reached..
Mon Dec 05 11:42:53 +0000 [cluster1-01: wafl_exempt01: wafl.sis.clone.error:info]: Error 59 occurred at line 4176 with src_fsid 1035, src_fileid 36332, dst_fileid 53053, dir_fileid 0 in volume vol1q1.