Netapp/IBM NAS file system on Volume xxx is out of inodes
use "df -i" on the client to check the inodes.
xxxxx:/vol/home01 14199161888 3250047496 78% 31876688 100% /home
On Netapp/IBM NAS, double the size:
xxxxx02> maxfiles home01
Volume home01: maximum number of files is currently 31876689 (31876689 used).
xxxxx02> maxfiles home01 63753378
The new maximum number of files specified is more than twice as big as
it needs to be, based on current usage patterns. This invocation of the
operation on the specified volume will allow disk space consumption for
files to grow up to the new limit depending on your workload. The maxfiles
setting cannot be lowered below the point of any such additional disk space
consumption and any additional disk space consumed can never be reclaimed.
Also, such consumption of additional disk space could result in less
available memory after an upgrade.
The new maximum number of files will be rounded to 63753378.
Are you sure you want to change the maximum number of files? yes
xxxxx02> maxfiles home01
Volume home01: maximum number of files is currently 63753378 (31876689 used).
DO not increase the maxdirsize which does not increase the inodes.
xxxxx02> vol options home01 maxdirsize 3200000
xxxxx02> vol options home01
nosnap=off, nosnapdir=off, minra=off, no_atime_update=off, nvfail=off,
ignore_inconsistent=off, snapmirrored=off, create_ucode=on,
convert_ucode=on, maxdirsize=3200000, schedsnapname=ordinal,
fs_size_fixed=off, guarantee=volume, svo_enable=off, svo_checksum=off,
svo_allow_rman=off, svo_reject_errors=off, no_i2p=off,
fractional_reserve=100, extent=off, try_first=volume_grow,
read_realloc=off, snapshot_clone_dependency=off, dlog_hole_reserve=off,
nbu_archival_snap=off
xxxxx:/vol/home01 14199161888 3250047496 78% 31876688 100% /home
On Netapp/IBM NAS, double the size:
xxxxx02> maxfiles home01
Volume home01: maximum number of files is currently 31876689 (31876689 used).
xxxxx02> maxfiles home01 63753378
The new maximum number of files specified is more than twice as big as
it needs to be, based on current usage patterns. This invocation of the
operation on the specified volume will allow disk space consumption for
files to grow up to the new limit depending on your workload. The maxfiles
setting cannot be lowered below the point of any such additional disk space
consumption and any additional disk space consumed can never be reclaimed.
Also, such consumption of additional disk space could result in less
available memory after an upgrade.
The new maximum number of files will be rounded to 63753378.
Are you sure you want to change the maximum number of files? yes
xxxxx02> maxfiles home01
Volume home01: maximum number of files is currently 63753378 (31876689 used).
DO not increase the maxdirsize which does not increase the inodes.
xxxxx02> vol options home01 maxdirsize 3200000
xxxxx02> vol options home01
nosnap=off, nosnapdir=off, minra=off, no_atime_update=off, nvfail=off,
ignore_inconsistent=off, snapmirrored=off, create_ucode=on,
convert_ucode=on, maxdirsize=3200000, schedsnapname=ordinal,
fs_size_fixed=off, guarantee=volume, svo_enable=off, svo_checksum=off,
svo_allow_rman=off, svo_reject_errors=off, no_i2p=off,
fractional_reserve=100, extent=off, try_first=volume_grow,
read_realloc=off, snapshot_clone_dependency=off, dlog_hole_reserve=off,
nbu_archival_snap=off
Comments