Quote:
Originally Posted by
Siva SQL
I have been advised by our Unix System administrator that "I-Noe Usage Warning threshold of 5%" set after witnessing an issue in the past when our production batch cycle slowed down to the i-node count on this server reaching 7%.
We have a warning in place so that we can try to take action before it reaches that point again.
Would appreciate and views on how come I-node usage of 7% can impact on the Server slowness?
Server is running on HP-UX 11.31 11i v3.
This is completely backwards! Depending on file system type, there could be issues if the i-node FREE percentage dropped to 7%, but there can't possibly be a performance problem caused by having too many i-nodes free. The warning they have chosen to give is complaining when things are in GREAT shape.
When you get to 100% used on a filesystem that doesn't automatically allocate more i-nodes when you run out, you can't create any more files. This is a HUGE problem, but they won't generate a warning in this case (100% used) they are only generating a warning when everything is great. Tell them in no uncertain terms that if they want to issue a warning when there are less than 10% free i-nodes that would be great; but the way to test for that is to look for %iused values of 90% or higher; not 5% or lower!
As has already been noted here; for some filesystems (ones that allocate i-nodes when needed), this test is completely bogus. Issuing warnings when %used values are greater than 90% always makes sense; issuing warnings for %iuse values greater than 90% makes sense on some filesystem types. Issuing warnings when either of these values is less than 5% shows a complete lack of understanding what those values mean!