Skip to main content
NetApp Knowledge Base

How to capture part of an ONTAP coredump which is failing to save

Last Updated:

Applies to

  • ONTAP 9


We have seen instances of ONTAP coredump sprayed across multiple disks which could not be saved because one of the disks errored out when reading.  When ONTAP saves a core, it creates a temporary file in the directory /mroot/etc/crash.  If the coredump save errors out, ONTAP deletes the temporary file.  The following action plan was developed to capture as many blocks of the temporary coredump file as possible by triggering snapshots of the nodes root volume.  


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.
Scan to view the article on your device