This would be better asked on a Redhat list, but I have had this same
problem. The problem is most likely the maximum number of inodes in use.
For some reason ClearCase on Redhat 7.0 uses more than the standard maximum
of inodes (as found in /proc/sys/fs/inode-max). I believe that the standard
maximum is around 16384. If you look at inode-nr, you will see the maximum
open inodes, then the number of open inodes. On my system, I was getting
more open inodes than the maximum. This was the problem. I thus changed
the inode-max number to 65536 (and I changed the file-max to 16384 instead
of 4096). To do this change (and make it permanent) I put two lines into
/etc/rc.d/rc.local:
echo 16384 > /proc/sys/fs/file-max
echo 65536 > /proc/sys/fs/inode-max
I have not had a problem since.
Forrest
> -----Original Message-----
> From: Prabhu Gurudas Panchmal [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 17, 2001 2:37 PM
> To: [EMAIL PROTECTED]
> Subject: Problem with Linux kernel: Grow Inodes... Please help....
>
>
> Hi
> I am not sure if this is the right group to send this to.
>
> Any help in resolving this problem of grow_inodes is appreciated.
>
> After a number of days I get this problem on my Linux box running
> RedHat 7.0 (2.2.16-22).
> I am also running Clearcase on this Linux box. I am not sure if
> this is a problem with ClearCase.
>
> Below is the error message from /var/log/messages file. The "df
> -i " command reports 12% usage
> of Inodes and a lot of Inodes are free.
>
> kernel: grow_inodes: inode-max limit reached
> Apr 17 04:06:24 kernel: __nfs_fhget: iget failed
> Apr 17 04:06:24 kernel: grow_inodes: inode-max limit reached
>
> Thanks
> Prabhu
>
> --
> _
>
