sar -v and ninode results

[Dietmar Konermann · Accepted solution]

Allien,

let me try to shed some light onto this.

The inod-sz metric that sar -v shows is somewhat inconsistent.

The maximum value is take from stat_getstatic's pst_max_ninode metric. This is equal to ninode, which is clearly the size of the HFS-only inode cache.

The current value is pstat_getdynamic's psd_activeinodes metric. This is the number of active inodes for BOTH, HFS and VxFS! The printed value is resticted to be not larger than pst_max_ninode. :) So it is clear, that you see a current==max situation on most of the systems.

In summary, you can forget this sar report at all. OK, it may be useful if you want to check ninode. :)

Since only /stand is usually HFS, there's no need to increase it at all. I usually set it fixed to say 1024.

The VxFS inode cache size is dynamic. However, the maximum size can be restricted using the vx_ninode tunable. By default this is 0, which means that the maximum is derived from physmem at boot time. For large memory systems it is often a good idea to restrict vx_ninode to say 30000.

Best regards...
Dietmar.