Netapp: Flexgroup volume vs. flex volume and inodes limit

Learn Storage, Backup, Virtualization,  and Cloud. AWS, GCP & AZURE.

............................................................................................................................................................................

Netapp: Flexgroup, Inodes limit, Volumes count- NFS

Flexgroup and Files Count:

NFSv3 in ONTAP uses 32-bit file IDs by default. 32-bit file IDs are limited to 2,147,483,647 maximum unsigned integers. With the two-billion inode limit in FlexVol, this value fits nicely into the architecture. 

However, because NetApp FlexGroup volumes can officially support up to 400 billion files in a single container (and theoretically, many more), the implementation of 64-bit file IDs was needed. 64-bit file IDs support up to 9,223,372,036,854,775,807 unsigned integers. The 64-bit file identifier option is off by default. 

This was by design, to make certain that legacy applications and operating systems that require 32-bit file identifiers were not unexpectedly affected by 34 NetApp ONTAP FlexGroup Volumes .

 ONTAP changes before administrators could properly evaluate their environments. Check with your application and OS vendor for their support for 64-bit file IDs before enabling them. Alternatively, create a test SVM and enable it to see how applications and clients react with 64-bit file IDs. Most modern applications and OSes can handle 64-bit file IDs without issue.

If a FlexGroup volume does not exceed two billion files, you can leave this value unchanged. However, to prevent any file ID conflicts, the inode maximum on the FlexGroup volume should also be increased to no more than 2,147,483,647.

You are Welcome :)

Source: www..netapp.com