Hi,
I do not know what it might be, but if I were in your place I would run fsck
and hope that the inodesstuff gets fixed. Or try df -i ... to check if you
"accidentally" ran out of inodes. Every filesystem has a limited # of inodes
only.
--Joerg
am 18.05.2001 17:11 Uhr schrieb Antonio Paulo Salgado Forster unter
aforster@br.ibm.com:
> Hello,
>
> Today I've found my cache box (linux 2.2.17 -Squid Version
> 2.3.STABLE4) locked up.. Searching in the system logs, I found heaps of the
> following:
>
> May 17 19:24:50 cache kernel: iput: device 00:00 inode 31095339 still has
> aliases!
> May 17 19:24:51 cache kernel: iput: device 00:00 inode 31095407 still has
> aliases!
> May 17 19:24:51 cache kernel: iput: device 00:00 inode 31095432 still has
> aliases!
> May 17 19:24:52 cache kernel: iput: device 00:00 inode 31095442 still has
> aliases!
> May 17 19:24:53 cache kernel: iput: device 00:00 inode 31095460 still has
> aliases!
> May 17 19:24:53 cache kernel: iput: device 00:00 inode 31095486 still has
> aliases!
> May 17 19:24:54 cache kernel: iput: device 00:00 inode 31095497 still has
> aliases!
> May 17 19:24:54 cache kernel: iput: device 00:00 inode 31095502 still has
> aliases!
> May 17 19:24:54 cache kernel: iput: device 00:00 inode 31095507 still has
> aliases!
>
> The squid logs didnt show anything...
>
> Does anybody know what that may be?
>
> Thanks!
>
> Forster
>
>
>
Received on Fri May 18 2001 - 13:30:57 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:00:11 MST