Skip to main content
NetApp Knowledge Base

CONTAP-796548: Node Panic Due to Kernel Process Identifier Pool Exhaustion

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

Issue

On nodes running multiple ONTAP versions, a node may panic and reboot automatically after an extended period of continuous uptime. A finite pool of internal process identifiers tracked by the operating system kernel gradually becomes depleted over time. When the pool is nearly exhausted, starting any new system process can stall while the kernel searches for an available identifier, causing a CPU to become unresponsive until the node watchdog detects the hang and panics the node.
Observed panic string:
PANIC: thread (sh) on cpu 18 hung for 4001 milliseconds in process sh
 

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.