<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">Em 17/02/2017 09:44, Amos Jeffries
escreveu:<br>
</div>
<blockquote
cite="mid:20ab0957-db57-b6c0-a255-8cd1c709e2e1@treenet.co.nz"
type="cite">
<pre wrap="">On 16/02/2017 10:40 a.m., Heiler Bemerguy wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Is it normal, on every restart?
</pre>
</blockquote>
<pre wrap="">
Well, this is a check that is only performed on restart. So in a way it
is "normal" that it occurs on restart. It should not happen at all
though. AFAIK, it is a sign of cache corruption...</pre>
</blockquote>
<br>
Right. But cache corruption, by a hardware/disc error, can not be.
These disks were formatted and tested, 3 times already, while trying
to solve this errors and some other stuff.<br>
<br>
<br>
<blockquote
cite="mid:20ab0957-db57-b6c0-a255-8cd1c709e2e1@treenet.co.nz"
type="cite">
<blockquote type="cite">
<pre wrap="">maximum_object_size 2 GB
cache_dir rock /cache 120000 min-size=0 max-size=12288 slot-size=12288 max-swap-rate=250 swap-timeout=350
cache_dir rock /cache2 120000 min-size=10240 max-size=65536 max-swap-rate=250 swap-timeout=360
</pre>
</blockquote>
<pre wrap="">
These caches cannot store objects larger than 64KB. So where do you
expect the 64KB thru 2GB objects to go?</pre>
</blockquote>
<br>
There are another cache_dirs just below these, like:<br>
cache_dir rock /cache3 120000 min-size=65537 max-size=262144
max-swap-rate=250 swap-timeout=380<br>
cache_dir rock /cache4 120000 min-size=262145 max-swap-rate=250
swap-timeout=500<br>
<br>
<br>
<blockquote
cite="mid:20ab0957-db57-b6c0-a255-8cd1c709e2e1@treenet.co.nz"
type="cite"><br>
<blockquote type="cite">
<pre wrap="">2017/02/15 18:38:50 kid7| WARNING: Ignoring cache entry due to a SIZE
MISMATCH 5852!=5853
2017/02/15 18:38:51 kid7| WARNING: Ignoring cache entry due to a SIZE
MISMATCH 6223!=6222
2017/02/15 18:38:51 kid7| WARNING: Ignoring cache entry due to a SIZE
MISMATCH 4198!=4202
</pre>
</blockquote>
<pre wrap="">...
That last line means the rock database contains an object of size 4198
bytes, with 4202 bytes of data in it.
4202 > 4198. So 4 bytes of what? the next database slot? padding data?
You have any custom patches applied to this Squid? what version is it?
</pre>
</blockquote>
<br>
No patches. Squid Cache: Version 4.0.18 configure options:
'--enable-htcp' '--disable-maintainer-mode'
'--disable-dependency-tracking' '--disable-wccp' '--disable-snmp'
'--enable-inline' '--enable-async-io=32'
'--enable-storeio=aufs,rock' '--enable-underscores'
'--enable-removal-policies=lru,heap' '--enable-http-violations'
'--disable-ident-lookups' '--with-large-files' '--enable-ssl'
'--enable-ltdl-convenience' '--prefix=/usr' '--localstatedir=/var'
'--libexecdir=/lib/squid' '--srcdir=.' '--datadir=/usr/share/squid'
'--sysconfdir=/etc/squid' '--with-default-user=proxy'
'--with-logdir=/var/log' '--with-pidfile=/var/run/squid.pid'
'--with-filedescriptors=16384' '--with-aufs-threads=32'
'--disable-translation'<br>
<br>
My only <b><i>Suspicion</i></b> is the different slot-size from
kid7 (/cache). But these messages also appears on kid8 (/cache2),
although with much, MUCH less frequency..... (while
rebuilding/restarting, always)<br>
<br>
<pre class="moz-signature" cols="72">--
Best Regards,
Heiler Bemerguy
Network Manager - CINBESA
55 91 98151-4894/3184-1751</pre>
</body>
</html>