I'm rusty on solaris, but on Linux you can use a df -i to check the inode usage on the file systems. At one time I hacked out a quick inode.sh script to monitor for this condition after this same situation happened to me. If I locate it I can send it to you or the list. If you are going to build a file system for the hobbit history logs in the future, you can tune the file system when creating it to create more inodes than the ext3 or ufs default. I think when this happened to me I just stopped hobbit, moved the histlogs to a file system with a lot of inodes free and just soft linked it to get things working again. HTH.
Tony
Longina Przybyszewska wrote:
Hobbit (4.2 Solaris9) made the whole disk partition out of game because of "out of inodes" fail. Disk partition is 3.8Gb , used 1.7 Gb, available 2.1Gb. The directory /opt/hobbit/data/histlogs/ keeps huge amount of historical data about each hobbit client.
In my configuration I keep to the default values for history events.
What shall I look after, and which variables should be tuned to avoid that fail in the future? regards
Longina
--
Longina Przybyszewska, system programmer
Dept. of Math. & Comp. Sci. - IMADA
University of Southern Denmark, Odense
Campusvej 55,DK-5230 Odense M, Denmark
tel: +XX XXXX XXXX - http://www.imada.sdu.dk email: user-db0a93c0e294@xymon.invalid
--