Problem with inode-nr on 2.0.33

Daniel.Veillard@w3.org
Fri, 20 Feb 1998 14:25:06 -0500


Hi,

I'm having problems with the number of used inode in 2.0.33.

Lately I got suddenly a problem with a lack of inode in the kernel
it appeared first as in my console as:
------------------------
28!PCROND: can't open log file
/var/log/cron: Too many open files in system
CROND: can't write to log file
------------------------
I killed a few apps to regain some new descriptors, and increased
the number by echoing a large number to /proc/sys/kernel/inode-max.
It now reflect this value correctly (32768, the previous one was
approximately 2000). And this corrected the problem, great !

However 3 days have passed now and /proc/sys/kernel/inode-nr now
reflect something rather alarming:
~ -> cat /proc/sys/kernel/inode-nr
26272 25540
~ ->

This number has increased a lot in 3 days, I am unable to understand
why, and I'm afraid of being hit again by this problem. However it seem
to not have increased during the last 12 hours. There is definitely not
25000 inode currently open in my system. There is around 160 processus
running, sockstat reports sockets: "used 382 TCP: inuse 241 highest 467"
and listing /proc/[0-9]*/fd/ doesn't show that amount of open files.

Maybe it's just normal but it doesn't really seem so.

Here is my setup (rufus.w3.org) :
- Dual PPro 200, 256 MBytes mem
- Kernel 2.0.33, Adaptec 2940 UW and 1542 drivers, 2 EEPro Ethernet cards
- Redhat 5.0 + all updates
- AFS afs-3.3a-2.0.32.i386.rpm using the SMP module
- used for backups
- serves a reasonable number of HTTP and FTP requests, but this
is not what I would call a busy site.

Thanks,

Daniel

-- 
Daniel.Veillard@w3.org | W3C  MIT/LCS  NE43-344  | Today's Bookmarks :
Tel : +1 617 253 5884  | 545 Technology Square   | Linux, WWW, Java,
Fax : +1 617 258 5999  | Cambridge, MA 02139 USA | badminton, Kaffe,
http://www.w3.org/People/W3Cpeople.html#Veillard | HTTP-NG and Amaya.

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu