Skip to main content
NetApp Knowledge Base

Call home for VOLUME CRITICALLY OUT OF SPACE ERROR

  1. Last updated
  2. Save as PDF
Views:
262
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

ONTAP 9.8P1

Issue

  • Autosupport Alert: HA Group Notification (VOLUME CRITICALLY OUT OF SPACE) EMERGENCY
  • VOLUME CRITICALLY OUT OF SPACE ERROR is seen in EMS logs.

Thu Mar 30 02:20:06 [Node01: wafl_spcd_main: callhome.vol.space.crit:EMERGENCY]: Call home for VOLUME CRITICALLY OUT OF SPACE ERROR.
Thu Mar 30 02:20:06 [Node01: wafl_spcd_main: vol.phys.overalloc:EMERGENCY]: Aggregate node01_aggr0 is physically overallocated, using 109.0%% logical space and 104.4%% physical space.

  • Vol0 space utilization from the df output:

::> df

Filesystem              kbytes       used      avail capacity  Mounted on
/vol/vol0/           150705588   74897508   75808080      50%  /vol/vol0/
/vol/vol0/.snapshot    7931872   12733532          0     161%  /vol/vol0/.snapshot

  •  Aggregate space utilization is 100% full.

::> df -A

Aggregate               kbytes       used      avail capacity  
node01_aggr0         167648972  167648972          0     100%  
node01_aggr0/.snapshot 8823628    1309204    7514424      15%  

  • High Delayed Frees count looking at volume footprint within the aggregate, the value increases over time and never decreases. 

::> volume show-footprint

Volume : vol0
 
      Feature                                           Used      Used%
      --------------------------------      ----------------      -----
      Volume Data Footprint                           70.2GB        42%
      Delayed Frees                                    104GB        62%
 
      Total                                            174GB       104%

 

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.