Skip to main content
NetApp Knowledge Base

Inode Cache - file operations suspend heavily creating massive latency

Last Updated:

Applies to

  • ONTAP 9
  • NFS
  • SMB


Overall very poor performance for file/directory based operations, with the following possible symptoms:

  • Many long running READDIR/READDIR+ requests could be identified from a packet trace, it could take up to tens of seconds, or even hundreds of seconds in the worst case scenario 
    • Note:  The same applies to SMB2 QUERY_DIRECTORY requests or its equivalents in other SMB versions
  • High latency for other file operation types, such as GETATTR, LOOKUP, ACCESS, etc. 
  • Timeout on the NFS/SMB clients
  • Extremely high latency reported from various Performance Monitoring tools
  • The following wafl.readdir.expired error message from EMS could indicate the presence of a similar issue

[<node_name>: wafl_exemptxx: wafl.readdir.expired:error]: A READDIR file operation has expired for the directory associated with volume <volume_name>/@vserver:<vserver_uuid> Snapshot copy ID xx and inode <inode_number>.



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.