Upstream work recently indicates that this may also be related to
cache_swap_high garbage collection issues.
BUT we still need information about what HDD format has been used, and
now also what traffic rates are happening at the time of overflow.
Amos
What filesystem type is in use for the device the cache_dir is stored on?
Upstream have known issues with ZFS and XFS where the underlying FS uses
different amounts of storage space for files than gets reported to
Squid. This usually results in smaller on-disk than Squid is aware, but
it could as
Hello,
I can confirm this behavior. It occurs simply during normal usage.
I am using:
cache_dir aufs /var/spool/squid3 1 16 32
However the cache dir on one host was way over that, close to 30 GB. Luckily
that partition still had a considerable amount of free space.
--
With respect,
Hi Petter,
Thanks for your bug report.
Can you please provide some more details so when can track down where the issue
comes from?
* Is there any other file in /var/spool/squid3?
* Can you provide the output of squidclient mgr:storedir”?
Best regards,
L
--
Luigi Gangitano --
Package: squid3
Version: 3.3.8-1.2
Severity: important
User: debian-...@lists.debian.org
Usertags: debian-edu
The size limitation specificed in the cache_dir statement in the squid
configuration seem to be ignored, as squid uses more than the provided
space on the disk an exits when it is unable
5 matches
Mail list logo
