I have 25000 max inodes but 23492 are in use...

[Garrin Thompson]

I have 25000 max inodes but 23492 are in use accouding to sar -v 3 3. Is this a potential problem? I was just reading this post and others as a learning tool and can't tell how to reply to those who reply, so that is why this doesn't really answer any questions, but asks one instead. What will happen if all inodes get used up? Should I increase my maximum inodes since so many are being used?

[Brian M. Fisher]

The value you see of 25000 inodes is controlled by thr ninode kernel parameter, which could be increased.

ninode defines the number of slots in the inode table, and thus the maximum number of open inodes that can be in memory. The inode table is used as a cache memory.

Brian
<*(((>< er

[Garrin Thompson]

So it would behoove me to change the maximum value to a higher value, well above where it is averaging now, to saving me from future problems?

[Brian M. Fisher · Accepted solution]

It is not uncommon to see what appears to be a ?maxed out? value for
inode-sz column. The number to the left of the / is the number of
inodes open in the inode table cache and the number on the right is the maximum
number of inodes that can be open in the inode table cache determined from the
value of ninode in the running kernel. The HP-UX OS actually tries to
keep this value at the maximum for performance reasons. As more inodes are
cached, the inode retrievals (on average) will be faster. Seeing this value in
inode-sz to be equal to your ninode value is not something to be overly
concerned about. The system will maintain the cache and add/delete inode
entries as needed. This is unlike the proc-sz and file-sz columns
from the sar output which show hard limits. When these limits are
reached, new processes cannot not be started or additional files cannot be
opened. The inode-sz column refers to a cached table, and it is expected
that having this value ?maxed out? should not prevent users on the system from
extracting inode information from inodes not available in the cache. That
being said, tuning ninode to be a smaller or larger value to allow for a
smaller or larger inode cache table can have a neglibile effect on performance
in some environments.

Per document#KBRC00001929
http://us-support2.external.hp.com/cki/bin/doc.pl/

Brian
<*(((>< er