Skip to main content
NetApp Knowledge Base

CONTAP-484943: Some NFS ops against qtrees taking 5 minutes on 9.16.1

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

Issue

  • After running or upgrading to 9.16.1, occasional NFS ops against qtrees are taking up to 5 minutes before getting a response.
  • Linux clients with default timeo of 600 (60 seconds), and default retrans of 2 would likely see an NFS server not responding error messages after 3 minutes, and then NFS server ok 2 minutes later.
  • Applications such as IBM MQ, which require faster response times, may be impacted.
  • To confirm that the issue is being seen from ONTAP perspective:

    1. first check for hourly EMS message indicating any number of NFS operations taking over 60 seconds:
      • Nblade.NfsResponseTraceTriggerHourly:debug]: params: \{'responseCount': '14', 'trigger': '60'}

    2. If OPS taking > 60 seconds are noted, enable nfs server traces:
      • set diag; nfs server modify -vserver * -trace-enabled true

    3. Look for ems events showing NFS process time (procTime) taking close to 300 seconds.
      • Nblade.NfsResponseTraceTrigger:debug]: params: \{'clientAddr': '10.1.1.2', 'op': 'NFSv4 COMPOUND', 'vserverId': '#', 'procTime': '297', 'trigger': '60'}


Note:
  • To be exposed to this issue, systems must be running ONTAP 9.16.1 (without the fix or workaround for this issue deployed) and must be using qtree exports over NFS.
  • This issue is more likely to be seen on higher-end systems with high CPU counts due to the increased concurrency these systems allow.

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.