Re: [squid-users] Bad behavior when cache_dir is full

No, cache_dir directory i a mount point (exclusive for Squid cache_dir)
and there is plenty space in the logs file system.

Is there a parameter I may have missed that makes Squid not die on write error in cache_dir?

John Sloan's suggestion of a temporary proxy-only mode may be the best solution..

Pål

----------------------------------------------------------------
Addr: Pål Baltzersen, ElTele Øst AS, Sandakervn. 114B, N-0483 Oslo.
Phone: +47 23 18 10 00 Direct: +47 23 18 11 74
fax: +47 23 18 10 01 Mobile: +47 93 08 11 74
mail: pb@ost.eltele.no pal.baltzersen@ost.eltele.no

>>> Chris Tilbury <Chris.Tilbury@warwick.ac.uk> 14:39:49 18.02.99 >>>
On Thu, Feb 18, 1999 at 10:44:05AM +0100, Pål Baltzersen wrote:

> Disk fragmentation problem is a known issue on Solaris2.6
> but couldn't Squid handle this more robust than:
>
> 1999/02/18 10:08:14| diskHandleWrite: FD 30: disk write error: (28) No space left on device
> FATAL: Write failure -- check your disk space and cache.log
> Squid Cache (Version 2.1.PATCH2): Terminated abnormally.

I'm guessing here, but you probably have your cache swap logs on the
same disks as your actual cache?

You really don't want this. Move it/them somewhere else. Squid copes
just fine when a cache disk fills up, provided it can still write
logs. It's only when it fails to be able to write the swap log(s) hat
I've seen this problem arise.

Cheers,

Chris

-- 
Chris Tilbury, UNIX Systems Administrator, IT Services, University of Warwick
EMAIL: cudch+s@csv.warwick.ac.uk PHONE: +44 1203 523365(V)/+44 1203 523267(F)
                            URL: http://www.warwick.ac.uk/staff/Chris.Tilbury