Skip to main content
NetApp Knowledge Base

Reallocation process stopped: relocation.nospaceSnap error

not set
Last Updated:

Applies to

  • ONTAP 9+ 
  • Clustered ONTAP 8


  • Reallocation stopped because there is insufficient snapshot free space.
  • When reallocation for a volume is started it stops with an error insufficient snapshot free space immediately or after running for a while.
Thu Mar 12 01:47:32 IST [Node-Name: scan_frag_measure_wkr: wafl.reallocate.check.high:info]: Allocation check on 
'volume-name' is 2, hotspot 25 (threshold 4), so will reallocate.

Thu Mar 12 01:47:33 IST [Node-Name: wafl_exempt07: wafl.scan.relocation.nospaceSnap:error]: Reallocate scan for volume 
volume-name has stopped because there is insufficient snapshot free space.


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.