Hi Vladimir,
It is interesting that the manpage for maxfiles doesn't state anything about used files:
maxfiles increases the number of files that a volume can hold, as close as possible to max. File inodes are stored in blocks, and the filer may round the requested max number of files to the nearest block.
Once increased, the value of max can never be lowered, so the new value must be larger than the current value.
The value cannot be changed for a flexcache volume.
If no argument is specified, maxfiles displays the current value of max for all volumes in the system. If just the vol_name argument is given, the current value of max for the specified volume is displayed. For a flexcache volume, the origin volume's value is displayed.
Because each allowable file consumes disk space, and because the value of max can never be reduced, increasing max consumes disk space permanently. Increasing the max number of files to a large value can also result in less available memory after an upgrade. This means, you might not be able to run WAFL_check. If maxfiles identifies a new size as unreasonably large, it queries the user to verify that the new value is correct.
The filer's df command (see na_df(1)) can be used to determine how many files have currently been created in the file system.
I would compare if the df information matches the API information. The used files in the maxfiles could be a hold-over.
Regards,
- Rick -
