On 12/01/11 20:12, Drunkard Zhang wrote:
I'm testing squid-2.7STABLE9 + COSS + ext4 + SSD now.
When enlarge the coss, eg: from 10240 to 20480, I can see success in
cache.log, but the coss file on disk did not change, after 3 times of
"squid -k reconfigure" the coss file size changed.
How long did you wait? it could be that Squid was doing a long resize in
the background. This is a guess supported by the change actually happening.
But some times later, the squid process exited, with nothing left in
cache.log. Just once in cache.log I found:
2011/01/12 11:10:04| assertion failed: coss/store_io_coss.c:215:
"cs->curstripe< (cs->numstripes - 1)"
So, I wondering if resize of coss online is supported perfectly, that
we can use it without anxiety.
BTW, is shrink of coss filesystem is supported? If it is, do I have to
do it online, or offline? By online, I means operates without restart
squid process, and the offline means opposite.
I think you need to try offline change. Via a stop, squid -z and restart
sequence.
With squid-2.7STABLE9 + COSS + btrfs + SSD, reload can cause process
to stuck, with 100% CPU usage per squid process. I caught these info
in cache.log once:
2011/01/09 14:56:44| Killing RunCache, pid 59502
2011/01/09 14:56:44| kill 59502: (1) Operation not permitted
And kill of the process will make the process into a zombie. The
defunct process still using 100% CPU, which wasn't show in ps.
squid75 ~ # ps -eo pid,%cpu,cmd --sort=c
59343 2.7 [squid]<defunct>
59505 2.8 [squid]<defunct>
59380 2.9 [squid]<defunct>
59474 2.9 [squid]<defunct>
42558 3.4 [btrfs-endio-1]
43717 3.7 (squid) -YC -D -f squid73.conf
43925 4.0 (squid) -YC -D -f squid74.conf
42520 4.3 (squid) -YC -D -f squid75.conf
51532 4.4 (squid) -YC -D -f squid77.conf
18014 5.9 (squid) -YC -D -f squid72.conf
FWIW;
I think you will very much want to play with the squid-3.2 "RockStore"
code being written by The Measurement Factory guys. Contact Alex for
ways to get a current working version.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.10
Beta testers wanted for 3.2.0.4
