> 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.
>From your description it looks like there's an inode leak, as that's a huge
number of inodes to be allocated. From your setup the only unusual entry seems
to be the AFS filesystem, so possibly there's a problem there.
Has anyone else on the list here had an inode problem with AFS? (Or
alternatively, used AFS extensively _without_ a problem?)
Regards,
Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu