[squid-users] WARNING: Disk space over limit

Yuri yvoinov at gmail.com
Tue Jul 11 22:47:01 UTC 2017 


12.07.2017 4:34, Yuri пишет:
>
> 12.07.2017 3:25, Eliezer Croitoru пишет:
>> Hey,
>>
>> If you are using a single process ie not SMP(default) use aufs instead of diskd cache_dir.
>> It's much more stable and efficient then diskd(to my knowledge).
> Not sure about you knowledge. Diskd is simple designed for another OS
> than Linux. On appropriate platform it is not only stable, but quite
> efficient than aufs. :)
>> Eliezer
>>
>> ----
>> Eliezer Croitoru
>> Linux System Administrator
>> Mobile: +972-5-28704261
>> Email: eliezer at ngtech.co.il
>>
>>
>>
>> -----Original Message-----
>> From: squid-users [mailto:squid-users-bounces at lists.squid-cache.org] On Behalf Of erdosain9
>> Sent: Tuesday, July 11, 2017 17:25
>> To: squid-users at lists.squid-cache.org
>> Subject: [squid-users] WARNING: Disk space over limit
>>
>> Hi to all.
>> Im having this warning
>>
>> 2017/07/11 11:37:44 kid1| WARNING: Disk space over limit: 17241692.00 KB >
>> 15360000 KB
>> 2017/07/11 11:37:56 kid1| WARNING: Disk space over limit: 16800692.00 KB >
>> 15360000 KB
>> 2017/07/11 11:38:07 kid1| WARNING: Disk space over limit: 16466860.00 KB >
>> 15360000 KB
>> 2017/07/11 11:38:19 kid1| WARNING: Disk space over limit: 16152960.00 KB >
>> 15360000 KB
>> 2017/07/11 11:38:30 kid1| WARNING: Disk space over limit: 15905772.00 KB >
>> 15360000 KB
>> 2017/07/11 11:38:41 kid1| WARNING: Disk space over limit: 15664684.00 KB >
>> 15360000 KB
>> 2017/07/11 11:38:52 kid1| WARNING: Disk space over limit: 15499404.00 KB >
>> 15360000 KB
>>
>>
>> Why is this happening?? why is over limit??
>>
>> [root at squid ~]# df -h
>> S.ficheros              Tamaño Usados  Disp Uso% Montado en
>> /dev/mapper/centos-root    48G    17G   31G  36% /
>> devtmpfs                  1,9G      0  1,9G   0% /dev
>> tmpfs                     1,9G   2,1M  1,9G   1% /dev/shm
>> tmpfs                     1,9G   8,5M  1,9G   1% /run
>> tmpfs                     1,9G      0  1,9G   0% /sys/fs/cgroup
>> /dev/sda1                 497M   143M  355M  29% /boot
>> tmpfs                     380M      0  380M   0% /run/user/0
> Where's the /var mountpoint?
>
>> SQUID.CONF
>>
>> cache_dir diskd /var/spool/squid 15000 16 256
> You specified 15000 megabytes for cache. So, reasonable
>
> WARNING: Disk space over limit: 17241692.00 KB >
> 15360000 KB
>
> Squid tries to save more than you specified.
>> cache_mem 1000 MB
>> maximum_object_size_in_memory 1 MB
>>
>> cache_swap_low 90
>> cache_swap_high 95
> and if you take a look onto your swap_hi/low values you can see it's not
> do replacement to the end of specified store limit.
>> Yes, it is over cache_dir... but why?? and how i correct this?
> Try to do two things. First - increase cache_dir formal size. Second -
> return
>
> cache_swap_low
>
> to it's default value.
>
> Because of "Premature optimization is root of all evils".
Ooooops, it default value is 90 :) My bad, too much nightly work :)

Well. Let's read squid.conf.documented:

#  TAG: cache_swap_low    (percent, 0-100)
#    The low-water mark for AUFS/UFS/diskd cache object eviction by
#    the cache_replacement_policy algorithm.
#
#    Removal begins when the swap (disk) usage of a cache_dir is
#    above this low-water mark and attempts to maintain utilization
#    near the low-water mark.
#
#    As swap utilization increases towards the high-water mark set
#    by cache_swap_high object eviction becomes more agressive.
#
#    The value difference in percentages between low- and high-water
#    marks represent an eviction rate of 300 objects per second and
#    the rate continues to scale in agressiveness by multiples of
#    this above the high-water mark.
#
#    Defaults are 90% and 95%. If you have a large cache, 5% could be
#    hundreds of MB. If this is the case you may wish to set these
#    numbers closer together.
#
#    See also cache_swap_high and cache_replacement_policy

Eviction starts when you cache achieves cache_swap_low. So, may be you
traffic is more than squid can be replaced between 90 and 95%. So, you
can try to decrease cache_swap_low. Or, review your caching policy to be
less aggressive. Or, increase cache_dir limit. Or all together.


>
>>
>>
>> --
>> View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/WARNING-Disk-space-over-limit-tp4683055.html
>> Sent from the Squid - Users mailing list archive at Nabble.com.
>> _______________________________________________
>> squid-users mailing list
>> squid-users at lists.squid-cache.org
>> http://lists.squid-cache.org/listinfo/squid-users
>>
>> _______________________________________________
>> squid-users mailing list
>> squid-users at lists.squid-cache.org
>> http://lists.squid-cache.org/listinfo/squid-users
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20170712/3d4b5fab/attachment.sig>

More information about the squid-users mailing list