Skip to main content
NetApp Knowledge Base

Does Trident support configuring inodes on volume creation and expansion?

  1. Last updated
  2. Save as PDF
Views:
326
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
cloud
Last Updated:

Applies to

  • Astra Trident 21.07 or higher
  • ONTAP 9.13 or later

Answer

Trident does not support configuring inodes.
 
As alternative, these methods can be used to manage inodes:
  • Resize the volume. As volumes are thin provisioned by default, this doesn't consume any extra space.
  • Use the flexgroup driver. A flexgroup is backed by multiple volumes on the backend storage, which will make it more difficult to hit the inode limit.
  • Use ontap-san drivers (and therefore iSCSI). Billions of small files lead to a lot of performance overhead with metadata operations (file creation, access timestamps, ownership & permissions,...), which all have to go across the network with a remote filesystem such as NFS. These operations are local operations on block storage and therefore can be faster in such scenarios. Utilizing block storage also allows for local control over inodes.
  • Set a larger snapshot reserve in Trident config. This increases the size of the ONTAP volume vs. the actual size of the PVC, giving you more inodes. As volumes are thin provisioned by default, this also doesn't consume any extra space.

Additional Information

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.