Re: [squid-users] Re: cache_dir aufs min-size

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Sat, 23 Oct 2010 14:07:16 +1300

On 23/10/10 06:30, Costin Gusa wrote:
> Hi,
> I was wondering if someone could shed a light on my previous unanswered email.
> Thank you.
>
> On Tue, Oct 19, 2010 at 22:10, Costin Gusa<costinel_at_gmail.com> wrote:
>>
>> Hi,
>> I would like to limit the minimum object size in a cache dir
>> For this I have setup the following line in squid.conf:
>>
>> cache_dir aufs /var/spool/squid 65536 16 256 min-size=4MB

IIRC the "option=XX" parser has not yet been fixed to handled byte sizes
like that. The above means "minimum 4 bytes".

Your earlier "min-size=4194304" should have worked.

Run "more 00000000" on the small file and see what URL its saved from
and what the HTTP headers were.

It could be a few things:
  * one of a few internal files (netdb amd clientdb) which require
saving to disk somewhere and pick the first cache_dir.

  * a large file still arriving from the network.

  * unknown-length files which are assumed to have an extremely big size
until they have arrived. Which has not yet been erased.

>>
>> However looking at /var/spool/squid cache dir, I see smaller objects also:
>>
>> /var/spool/squid# ls -lah 00/00|grep K|head -n3
>> drwxr-x--- 2 proxy proxy 4.0K 2010-10-19 21:56 .
>> drwxr-x--- 258 proxy proxy 8.0K 2010-10-19 20:31 ..
>> -rw-r----- 1 proxy proxy 73K 2010-10-19 20:35 00000000
>>
>> I tried also with min-size=4194304 with no luck
>>
>> Is this an intended behaviour or am I misunderstanding this functionality?
>>
> [...]
>> ii squid-common 2.7.STABLE3-4.1lenny1 Internet object cache (WWW proxy c

Also, please try an upgrade to the backports.org version in case this is
a fixed bug already.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.8
   Beta testers wanted for 3.2.0.2
Received on Sat Oct 23 2010 - 01:07:21 MDT

This archive was generated by hypermail 2.2.0 : Sat Oct 23 2010 - 12:00:04 MDT