Hi, COSS in Squid-3 isn't stable. Please don't use it unless you're interested in forward porting the big changes made in the Squid-2.6 branch. Adrian On Thu, Feb 28, 2008, S.KOBAYASHI wrote: > Hi there > > I'm configuring coss cache file system on my squid. > However it doesn't work and I got a strange message in cache.log > Here it is. > 2008/02/28 16:56:00| Preparing for shutdown after 2 requests > 2008/02/28 16:56:00| Waiting 30 seconds for active connections to finish > 2008/02/28 16:56:00| FD 15 Closing HTTP connection > 2008/02/28 16:56:31| Shutting down... > 2008/02/28 16:56:31| FD 16 Closing ICP connection > 2008/02/28 16:56:31| storeDirWriteCleanLogs: Starting... > 2008/02/28 16:56:31| Finished. Wrote 1 entries. > 2008/02/28 16:56:31| Took 0.00 seconds (4545.45 entries/sec). > FATAL: Aiee! aio_write() returned error (22) FIXME and wrap file_write ! > > My squid environment is as bellow. > Redhat Enterprise 5.0 running 64bit mode > Squid.3-HEAD (latest) > 1 ./configure --prefix=/usr/local/squid --enable-icap-client > --enable-storeio=coss,ufs > 2 dd if=/dev/zero bs=1048576 count=1024 of=/cache/coss > 3 put and changed some parameters in the squid.conf > cache_dir coss /cache/ 1024 block-size=512 max-size=1048576 > cache_swap_log /usr/local/squid/var/logs/%s > 4 squid -z > 5 start squid > 6 send http packet by using wget, http_proxy="http://192.168.12.10:3128"; > wget -O /dev/null http://192.168.12.4/512B-7/00000000.dat > 7 send again it. > 8 glance the accesslog , and it's no problem. > 192.168.11.31 TCP_MISS/200 837...... > 192.168.11.31 TCP_MEM_HIT/200 ....... > 9 shutdown the squid then strange message shows up in the cache.log and > object was NEVER saved in the coss file. > > What should I do the next? > > Thank you, > > Seiji Kobayashi. > -- - Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support - - $25/pm entry-level VPSes w/ capped bandwidth charges available in WA -
