[squid-users] Squid2.4 + DISKD unstable in Linux?

Hi,

We deployed Squidv2.4s3 on 2 GNU/Linux 2.4.18rc2 machines almost a week
ago and have been experiencing some problems with it. The configuration
for squid2.4s3 (more or less) is as follows:
 ./configure --enable-dlmalloc \
             --enable-removal-policies \
             --enable-gnuregex
             --enable-snmp \
             --enable-kill-parent-hack \
             --enable-arp-acl \
             --enable-carp \
             --with-threads \
             --enable-storeio=diskd,aufs,ufs

A few days after the cache has been run, one of the diskd processes core
dumps (leaving a stack trace in syslog). This happens to both machines.
Another proxy, running squid2.2 on a similarly configured GNU/Linux
system, has been running reliably for weeks.

Are there some performance/reliability issues with diskd under the
GNU/Linux 2.4.x kernels? Using aufs instead of diskd causes squid to die
much faster. Or does this have to do with glibc (currently using 2.2.4-19) and other related libraries?

Any help is appreciated.

---------------------------------
Gino LV. Ledesma
Ateneo Cervini-Eliazo Networks (ACENT)
email : gino@cersa.admu.edu.ph
web : http://cersa.admu.edu.ph/
phone : (63)(2) 426-6001 ext. 5925
Received on Wed Feb 20 2002 - 02:08:18 MST