Skip to main content
NetApp Knowledge Base

CONTAP-36952: Filesystem operations involving more than 512 objects not completing

  1. Last updated
  2. Save as PDF
Views:
16
Visibility:
Customer
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Issue

  • Some operations, such as open operations issued from CIFS, might be improperly suspended when they encounter very long file path names, specifically longer than 512 path components.
  • This might also happen when enumerating a directory with more than 512 entries.
  • The problem is caused by a bug in the inode reader-writer locking infrastructure, which was recently introduced in the ONTAP 9.5 release.

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.