RESOLVED
kudos to John Clear who explained this behavior:
https://library.netapp.com/ecmdocs/ECMP1610211/html/GUID-E4A62DE4-E7A4-410E-...
Data ONTAP automatically sets the maximum number of public inodes for a newly created volume based on the size of the volume: 1 inode per 32 KB of volume size. When the size of a volume is increased, either directly by an administrator or automatically by Data ONTAP through the autosize feature, Data ONTAP also increases (if necessary) the maximum number of public inodes so there is at least 1 inode per 32 KB of volume size, until the volume reaches approximately 1 TB in size. Growing the volume greater than 1 TB in size does not automatically result in more inodes, because Data ONTAP does not automatically create more than 33,554,409 inodes. If you need more files than the default number for any size volume, you can use the volume modify command to increase the maximum number of inodes for the volume.
On Wed, Jan 25, 2017 at 10:21 AM, Momonth momonth@gmail.com wrote:
Hi All,
I've noticed the following on cDOT 9.0 production cluster:
na201::> df -h vol_imgstore03 Filesystem total used avail capacity Mounted on Vserver /vol/vol_imgstore03/ 90TB 60TB 29TB 67% /vol_imgstore03 na201svm-nfs10g-02 /vol/vol_imgstore03/.snapshot 0B 0B 0B 0% /vol_imgstore03/.snapshot na201svm-nfs10g-02 2 entries were displayed.
na201::> vol show vol_imgstore03 -fields files vserver volume files
na201svm-nfs10g-02 vol_imgstore03 59999998
So, volume's size is 90TB and its current max inodes possible is ~ 60M
na201::> vol size vol_imgstore03 +10g -vserver na201svm-nfs10g-02 vol size: Volume "na201svm-nfs10g-02:vol_imgstore03" size set to 90.01t.
Now, I just added 10G to the volume, expecting it's going to increase the "files" value respectively:
na201::> vol show vol_imgstore03 -fields files vserver volume files
na201svm-nfs10g-02 vol_imgstore03 59999998
However it's not the case.
Anyone knows what I'm missing here?
Cheers, Vladimir