Very Computer

1. kernel: grow_inodes: inode-max limit reached

Hello everybody,

I have the problem that every night at 00:00 my linux kernel produces
the message: "kernel: grow_inodes: inode-max limit reached"

I know how to read and modify the kernel parameters with the help
of the /proc filesystem and I am also aware of the fact that
a cron job could started at 00:00 could be responible (Although
I wasn't able to identify it)

But my question aims at another direction:

On the net I found a text
(http://linux.web.cern.ch/linux/lsr/doc/kernel/proc.txt)
where you can read, that file-handels and inode-handles are dynamically
allocated by
the kernel but not freed again?
Does somebody know whether this is on purpose for efficiency or
whatever,
or if it is a bug?

Secondly - and even more important for me - if the number of used inodes
is bigger then inode-max, does that mean that the system will no longer
work reliable, or is this pre shrink method mentioned in
(http://linux.web.cern.ch/linux/lsr/doc/kernel/proc.txt) something that
will work very well?

By the way, I can increase the values of inode-max and file-max. But are
there any upper limits for these values I cannot go beyond?

Thanks in advance for help or pointers...

Thanks in advance,

Markus Jochim

2. Ethernet config/detection problems

3. grow inodes: inode-max limit reached error.

4. Xatrix mission pack for Linux?

5. grow-inodes: inode-max limit reached

6. Linux & Compaq Presario 1235

7. inode overflow; c queue max run limit reached

8. Compact Flash Linux boot problem

9. Error: kernel: proc table reached allocation limit

10. telnet reach max user limit

11. Boot problem "VFS: file-max limit 8192 reached" anyone help?

12. Apache reached Max child limit

13. Using accept() when max FD limit has been reached