Skip to main content
NetApp Knowledge Base

CONTAP-618017: Container Block Reclamation scanner makes no progress

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Issue

  • Delayed free footprint remains >= 2%, for example:
    ::> volume show-footprint -fields delayed-free-footprint, delayed-free-footprint-percent
    vserver volume delayed-free-footprint delayed-free-footprint-percent
    -------- ------ ---------------------- ------------------------------
    MySVM MyVOlume 1.04TB 2%


  • The default options to trigger the block reclamation scanner are not changed and are default 1% and 2%:
    ::> node run -node local -command options wafl.df
    wafl.df.max.percent 2 (value might be overwritten in takeover)
    wafl.df.wm.percent 1 (value might be overwritten in takeover)


  • When tracking the delayed free usage per-volume over time, if increases >2% but never goes below <2%, for example:
    2025/12/12 Delayed Frees 1.63TB 3%
    2025/12/14 Delayed Frees 972GB 2%
    2025/12/16 Delayed Frees 988GB 2%
    2025/12/18 Delayed Frees 1001GB 2%
    2025/12/21 Delayed Frees 1009GB 2%
    2025/12/28 Delayed Frees 1013GB 2%
    2026/01/04 Delayed Frees 1014GB 2%
    2026/01/07 Delayed Frees 3.95TB 7%
    2026/01/18 Delayed Frees 1.04TB 2%

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.