Skip to main content
NetApp Knowledge Base

CONTAP-527915: Node Restart Caused by CPU Hang During File Lock Update

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

Issue

A storage node can restart when a process becomes stuck while updating internal file lock state. The stuck process holds the CPU long enough to trigger the system watchdog timer, which causes the node to generate a core file and reboot. The node logs the following message:
PANIC: process on cpu14 hung (wafl_exempt04) for 5003 milliseconds! in SK process wafl_exempt04 

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.