https://community.hpe.com/t5/operating-system-hp-ux/inode-table/m-p/2501423#M20962 The inode table is an in-core cache of current and recently opened HFS files. Note: HFS files. That means that for typical systems, the cache is seldom used (and often FAR TOO BIG) as /stand is the only HFS filesystem on the disk.<BR /><BR />Unless you have lots of HFS filesystems (hint: mount -p), the ninode parameter should NOT be a formula but set to about 500 ot 1000 as a fixed value. Because it is a cache, it has 1 entry for every UNIQUE file that is now or has been opened recently so it may look quite full. But typically, it will only have occupied slots when you access the /stand directory (ie, kernel buiding, including running SAM) Tue, 06 Mar 2001 12:36:36 GMT Bill Hassell 2001-03-06T12:36:36Z https://community.hpe.com/t5/operating-system-hp-ux/inode-table/m-p/2501422#M20961 "sar -v" reports that the ninode table is zero meanwhile nfile table value is high.<BR /><BR />Why ? Tue, 06 Mar 2001 10:33:06 GMT https://community.hpe.com/t5/operating-system-hp-ux/inode-table/m-p/2501422#M20961 Jdamian 2001-03-06T10:33:06Z https://community.hpe.com/t5/operating-system-hp-ux/inode-table/m-p/2501423#M20962 The inode table is an in-core cache of current and recently opened HFS files. Note: HFS files. That means that for typical systems, the cache is seldom used (and often FAR TOO BIG) as /stand is the only HFS filesystem on the disk.<BR /><BR />Unless you have lots of HFS filesystems (hint: mount -p), the ninode parameter should NOT be a formula but set to about 500 ot 1000 as a fixed value. Because it is a cache, it has 1 entry for every UNIQUE file that is now or has been opened recently so it may look quite full. But typically, it will only have occupied slots when you access the /stand directory (ie, kernel buiding, including running SAM) Tue, 06 Mar 2001 12:36:36 GMT https://community.hpe.com/t5/operating-system-hp-ux/inode-table/m-p/2501423#M20962 Bill Hassell 2001-03-06T12:36:36Z