Skip to main content
NetApp Knowledge Base

NFS hung/slowness issue when dealing with long path names with FPolicy enabled

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

Applies to

  • ONTAP 9.8 +
  • FPolicy Enabled

Issue

  • FPolicydoes not seem to be able to handle longer file paths in NFS.
  • ONTAP answers the client NFS request with an "NFS3ERR_JUKEBOX" error.
  • ONTAP event logs could throw messages like "Nblade.dBladeNoResponse.NFS: File operation timed outbecause there was no response from the data-serving node.Node UUID:XXXX, file operation protocol:NFS, client IP address: XX.XX.XX.XX, Opcode/Procedure: NFS3_RENAME(14)."
  • There could be slowness/high latency observed for the volume with long path name.
  • It is not required to have an external FPolicy server which is connected, even in the"disconnected" state the problem would occur.
  • A single path does not need to be very long - for emaple, in a SCREEN_REQ packet for a NFS_RENAME, if the same path name occurs multiple times , could lead to a large SCREEN_REQ packet (i.e., with a from/to path length of each around 3500 bytes the problem can be triggered with an NFS_RENAME).
     

 

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.