Skip to main content
NetApp Knowledge Base

Controller panic during ONTAP upgrade caused loss of data access

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

Applies to

  • ONTAP 9.3 - ONTAP 9.3P6
  • ONTAP 9.4 - ONTAP 9.4P1
  • Automatic Non-Disruptive Upgrade (ANDU)

Issue

  • Node goes down with the following panic string:

PANIC: process on cpu14 hung (wafl_exempt00) for 5001 milliseconds! in SK process wafl_exempt14 on release 9.3P6 (C)

  • The node may panic shortly after starting takeover of partner for ANDU process:

[controller02: svc_queue_thread: clam.notify.halt.result:debug]: CLAM was able to notify its HA partner node that the local node is undergoing a planned shutdown (reason: Local node shutting down). Error: 0

[controller02: cf_main: cf.fsm.firmwareStatus:info]: Failover monitor: partner Dumping core

 

 

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.