Skip to main content
NetApp Knowledge Base

CONTAP-365957: SMB workloads causing high inode/disk usage on a partcular FlexGroup constituent

  1. Last updated
    Apr 12, 2025
  2. Save as PDF
Views:
51
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:
4/12/2025, 4:21:05 AM

Issue

  • FlexGroup can place the directories/files on the FlexGroup constituent that is hosting the CIFS Share for SMB workloads. This happens when there is constant directory renames happening on that FlexGroup. This causes high inode and disk usage on that constituent alone compared to the others. This results in the SMB workloads being directed to that particular constituent causing bottlenecks leading to very high latency compared to the other constituents of the FlexGroup.

 
  • If the CIFS Share is pointing to the root of the FlexGroup, then the high inode/disk space will be on the 1st constituent 0001. If the CIFS Share is pointing to a directory witin the FlexGroup, then this high inode/disk space will be on the constituent that is hosting the last component of the directory path used in the CIFS Share.

 

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.