Skip to main content
NetApp Knowledge Base

NFS Server Not Responding and Widespread VM BSODs Due to CPU Starvation

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

Applies to

  • NFS
  • 9.15.1 CLUSTER-MODE

Issue

  • NFS clients (RHEL/OpenShift) reported “nfs server not responding, still trying"
  • Windows VM's experienced BSODs
  • EMS/system logs showed:

Sun Nov 02 01:34:14-0500 [dc1h20502:mgwd:rdb.node.starvation:error]: CPU starvation detected in the RDB.
Sun Nov 02 01:29:37-0500 [dc1h20502:ksmf_timeout_thread:ksmf.svc.watchdog:debug]: "kSMF service thread held >25(sec) by application for table ksmfRawZapi"
Sun Nov 02 01:30:25-0500 [dc1h20502:kernel:Nblade.nfsLongRunningOp:debug]: Detected a long running network process operation. The client IP address:port is 19.14.190.123:719...
Sun Nov 02 01:33:40-0500 [dc1h20502:CCMA-Scheduler:perf.ccma.workQ.overrun:debug]: Performance archiver cannot collect objects in a timely manner, for the 1 seconds period.

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.