Re: [squid-users] diskd problem

Hi Massod:

I running squid 2.4STABLE7 on redhat 7.3. and I asked the very same
question last week or the week previous. After monitoring the status for
a while, it became apparent that the unlink's may be failing because it
has to load up the cache_dir's before it starts removing files. In my
case once the cache_dir filled up to capacity, I could watch the stats and
see very few failures, if any failures, for unlink after that point.

I can't speak of the failures for create or open. I would recommend
waiting for the cache_dir to fill up, and then monitor whether the
failures for unlink are showing up. Act immediately if you see any funny
stuff in the logs though.

Hope that helps.

Thanks,

On Thu, 26 Dec 2002, MASOOD AHMAD wrote:

> Dear Squid users,
> I'm running Squid2.5 Stable1 with diskd cache
> filesystem on Redhat Linux 6.2 ext2 filesystem.
> Today I was seening my cachemgr logs and it was
> displaying like that..
>
> sent_count: 5006246
> recv_count: 5006246
> max_away: 4
> max_shmuse: 4
> open_fail_queue_len: 0
> block_queue_len: 0
>
> OPS SUCCESS FAIL
> open 891368 864524 26844
> create 220377 198107 22270
> close 1075608 1062624 0
> unlink 118684 61552 57132
> read 1488071 1461227 0
> write 1212138 1164899 0
> I'm seening that squid is going with unlink and create
> trouble can someone explain what are these and how can
> i solve the problem. Although cache is running fine.
>
> Best Regards,
> Masood Ahmad Shah
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>

Brian Seppanen
seppy@chartermi.net
906-228-4226 ext 23
Received on Thu Dec 26 2002 - 07:58:52 MST