Skip to main content
NetApp Knowledge Base

The /etc/crash/ directory reaches the maxdirsize limit

  1. Last updated
  2. Save as PDF
Views:
710
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • Clustered Data ONTAP

Issue

  • The following errors are seen in EMS:

Thu Aug 23 13:59:27 CST [filera:wafl.dir.size.max:warning]: Directory /vol/vol0/etc/crash/ reached the maxdirsize limit. Reduce the number of files or use the vol options command to increase this limit.  
...
Thu Aug 23 14:02:00 CST [filera:ucore.panicString:error]: 'coresegd: Received SIGABRT (Signal 6) at RIP 0x806308e5c (pid 7958, uid 0, timestamp 1535004120).'  

  • On checking /etc/crash in the diag Mode, it is confirmed that there are over 100K ucore files in the folder:

::*>node run -node filera -command "priv set diag; ls /etc/crash"
...
spmd.809.2014613136.1518883676.ucore   
spmd.47998.2014613136.1518883677.ucore   
spmd.48028.2014613136.1518883678.ucore   

  • A system core cannot be saved in such a case
  • A spare disk can be seen with 'Awating savecore' status if the controller panics in this state.

 

 

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.