跳转到主内容

在 NetApp AFF-A90 上更改 MaxQueueDepth 后 vSphere 主机崩溃

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

适用于

  • ONTAP 9
  • VMware vSphere ESXi
  • NFS 协议
  • Broadcom (VMware 母公司)

问题

  • 在 vSphere 环境中,NFS.MaxQueueDepth 和 NFS41.MaxQueueDepth 的值根据 NetApp KB 建议从 4294967295 更改为 128。
  • 此更改约 42 小时后,在 NetApp 存储(运行 ONTAP 9.15.1P6 的 AFF-A90)上运行虚拟机的所有 ESXi 主机相继出现 PSOD(紫屏死机),导致主机脱机,整个环境崩溃。
  • PSOD 引用了 InfSvc41Client 模块,涉及 NFS41_SchedTaskSubmit、NFS41FileOp 和 SwapIOClusterWriteWrapper。在其他存储设备上运行虚拟机的 ESXi 主机未受影响。
  • 该问题发生在 'RangeCluster' ESXi 主机上,这些主机在重新启动以应用 MaxQueueDepth 更改后出现了此问题。'PRODCluster' 主机未更改 MaxQueueDepth,因此未受影响。
  • PSOD 堆栈跟踪如下:
    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.