cache_dir problem.

why is it squid insists on going over the specified limit
for the cache_dir?

i am running squid-2.3-STABLE2.

here are the entries in squid.conf

#
cache_dir ufs /proxy3/cache 1500 16 256
cache_dir ufs /cache/cache 3000 24 256
# ^^^^
#
cache_dir ufs /webcache/cache 3000 24 256
# ^^^^
#
cache_dir ufs /webcache-2/cache 3000 24 256
# ^^^^
#
cache_swap_low 93
cache_swap_high 95
#
#
output of df -k:

sysadmin@tesla /opt/squid/logs>df -k
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/dsk/c0t2d0s0 2055705 1843927 150107 92% /proxy3
/dev/dsk/c2t0d0s0 4124422 3481453 601725 85% /webcache
/dev/dsk/c2t1d0s0 4124422 3379251 703927 83% /webcache-2
/dev/dsk/c0t3d0s0 4117942 3599347 477416 88% /cache
# ^^^^^^^
#

you'll notice i specified 3000 MB for /cache, /webcache, and /webcache-2
and yet the used space on the disks is 3.5GB, 3.48GB, and 3.37GB
respectively. it worked fine for a while, but recently i've been having
problems...the other day /cache was 97% full!!....there was < 2%
fragmentation on the disk. so why is squid insisting on going over the
cache_dir ammount??

i've re-created the filesystem on the /cache disk, recreated the dirs, and
rebuilt the cache and it still happened.

i am afraid of the disk(s) getting filled and squid crashing....
the 24 top level dirs are just for experimentation. the disks were
configured that way long before i started having this problem.

-andrew

#############################
Andrew Stack
UNIX Systems Administrator
State University at New Paltz
Phone: 914.257.3828

GNU/Linux - The choice of a GNU generation.....

One good solution to solve all your windows problems
is to install some flavor of UNIX. 8-)
#############################
Received on Wed May 10 2000 - 14:49:28 MDT