Skip to main content
NetApp Knowledge Base

vSphere hosts crash after MaxQueueDepth change on NetApp AFF-A90

Views:
4
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
NAS
Last Updated:

Applies to

  • ONTAP 9
  • VMware vSphere ESXi
  • NFS protocol
  • Broadcom (VMware parent company)

Issue

  • In the vSphere environment, the NFS.MaxQueueDepth and NFS41.MaxQueueDepth values were changed from 4294967295 to 128 based on NetApp KB recommendations.
  • Approximately 42 hours after this change, all ESXi hosts running virtual machines on NetApp storage (AFF-A90 running ONTAP 9.15.1P6) experienced rolling PSODs (Purple Screen of Death), resulting in the hosts going offline and a full environment crash.
  • The PSODs referenced the InfSvc41Client module with involvement of NFS41_SchedTaskSubmit, NFS41FileOp, and SwapIOClusterWriteWrapper. ESXi hosts running virtual machines on other storage devices were not affected.
  • The issue occurred on the 'RangeCluster' ESXi hosts after they were rebooted to apply the MaxQueueDepth changes. The 'PRODCluster' hosts, which did not have the MaxQueueDepth changed, were unaffected.
  • PSOD stack traces is:
    Failed to insert scheduling element:0x432f2aaadcdO into the priQ:0x432f2a404950. Reason:Limit exceeded
    NOT_IMPLEMENTED bora/vmkernel/sched/memsched_kmem.c:1436

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.