Skip to main content
NetApp Knowledge Base

SIS Clone operation failed to start with error Max Dense Limit is reached

Last Updated:

Applies to

  • Deduplication
  • SIS Clones


  • 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.

  • 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.


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.