Skip to main content
NetApp Knowledge Base

CONTAP-687329: ONTAP internal timer's dispatch race causes context timer stall

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

Issue

  • A rare timing condition in ONTAP's internal timer management can cause protocol-level timers on a single network processing thread to stop firing. Once triggered, the condition does not self-resolve and persists until the node is rebooted.
  • EMS errors show memory allocation being exceeded:
    • Thu Apr 01 00:00:00 -0700 [node-01: kernel: Nblade.cifs.budgetAllocFailure:error]: Memory Allocation failed for SpinNp Manager. The CIFS subsystem on this node has exceeded its allotment of 13999747891 bytes of node memory. CIFS subsystems that have consumed the most memory are FlexGroup Path/MSID Cache '11499898160 bytes', NameStr Objects '2427788176 bytes' and Accessed Path List '67663184 bytes'.
    • Thu Apr 01 00:00:00 -0700 [node-01: nblade2: Nblade.cifsMemExceeded:error]: The CIFS subsystem on this node has exceeded its allotment of 13999747891 bytes of node memory with currently 5627 memory allocation failures since boot time. This might result in unexpected CIFS application failures.

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.