Skip to main content
NetApp Knowledge Base

CONTAP-468663: Coredump manager tries to save a saved core

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

Issue

  • Two cores are available in this active-passive configuration running ONTAP version 9.12.1P11.
  • The passive node has a P3 Spare to its root aggregate.
    During the upgrade process, a P3 spare disk was pulled to save the core dump, even though the core had already been saved.
  • This action triggered a "low spares" condition, as the P3 disk on Node 02 became unavailable.

::> system node coredump show
Node:Type Core Name                                   Saved Panic Time
--------- ------------------------------------------- ----- -----------------
cluster-02:application
notifyd.1697.537118741.2023-11-08.06_18_37.ucore.bz2 true 11/8/2023 15:18:37
notifyd.89511.537118741.2023-11-08.06_23_41.ucore.bz2 true 11/8/2023 15:23:41

RAID Disk    Device      HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------    ------      ------------- ---- ---- ---- ----- --------------    --------------
Spare disks for block checksum
spare       0a.00.17P3    0a    0   17  SA:A   0   SSD   N/A 147102/301265408  147110/301281792 (Awaiting partner savecore)

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.