Re: [squid-users] Cache and min_size question: squid 2.7 with cache_dir aufs and min_size not working.

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Wed, 08 Jan 2014 11:45:25 +1300

On 2014-01-08 11:34, Soporte Técnico wrote:
> I need something of help here.
>
> I had a squid 2.7 running in freebsd.
>
> My cache_dir looks like:
>
> cache_dir aufs /sc 65535 16 128 min-size=16384
>
> I think min-size is in bytes, so 16384 = 16k.
>
> When i make ls –l in my cache_dir i see:
>
>     8 -rw-r-----  1 squid  squid   4.5k Jan  4 02:39 0000002F
>     8 -rw-r-----  1 squid  squid     5k Jan  2 10:46 00000030
>    12 -rw-r-----  1 squid  squid   8.2k Jan  2 12:23 00000031
>     8 -rw-r-----  1 squid  squid   7.0k Jan  2 10:46 00000033
>    16 -rw-r-----  1 squid  squid    12k Jan  2 12:23 00000034
>     8 -rw-r-----  1 squid  squid   4.5k Jan  2 10:46 00000035
>    24 -rw-r-----  1 squid  squid    23k Jan  2 10:46 00000036
>     8 -rw-r-----  1 squid  squid     7k Jan  2 10:46 00000037
>     8 -rw-r-----  1 squid  squid     6k Jan  2 12:23 00000038
>
>
> Objects with less size 16k ¿?
>
> Any help ¿?

* objects cached before you set that config option.

* objects with unknown-length (missing Content-Length: header).

* objects which changed size from >16K due to HTTP revalidation
replacement.
  - this one is an artifact of experimental fix for bug #7 in Squid-2.

* objects >16KB which were incompletely received, aborted and not yet
erased.
  - could happen on shutdown if the save failed and Squid not running
long enough to do the erase.

* objects where bug 2410 left a >16KB Content-Length header, but Squid
stored the short replacement object instead.

Amos
Received on Tue Jan 07 2014 - 22:45:29 MST

This archive was generated by hypermail 2.2.0 : Wed Jan 08 2014 - 12:00:04 MST