Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2009-01-17 Thread Adrian Chadd
2009/1/15 Mark Powell : >> Did you manage to get that FreeBSD 7 server working with COSS? > > Well did you :) Yes. At least in testing. I don't (yet) have a client running FreeBSD-7 and using COSS. > This problem still exists in the latest squid. Any likelihood of a fix, or > is COSS not recom

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2009-01-15 Thread Mark Powell
On Wed, 1 Oct 2008, Mark Powell wrote: On Fri, 12 Sep 2008, Adrian Chadd wrote: Well, I fixed the thing up under FreeBSD so it certainly was working for me at some point. I'm one server away from getting my polygraph test cluster going and I'll hopefully be installing that tomorrow; I'll make

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2008-10-01 Thread Mark Powell
On Fri, 12 Sep 2008, Adrian Chadd wrote: Well, I fixed the thing up under FreeBSD so it certainly was working for me at some point. I'm one server away from getting my polygraph test cluster going and I'll hopefully be installing that tomorrow; I'll make sure COSS gets a decent thrashing when t

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2008-09-12 Thread Adrian Chadd
Well, I fixed the thing up under FreeBSD so it certainly was working for me at some point. I'm one server away from getting my polygraph test cluster going and I'll hopefully be installing that tomorrow; I'll make sure COSS gets a decent thrashing when thats all up and running. adrian 2008/9/

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2008-09-12 Thread Mark Powell
On Fri, 12 Sep 2008, Amos Jeffries wrote: Can you report a bug on this please, so we don't forget it. with a stack trace when the crash is occuring. Already did, last year: http://www.squid-cache.org/bugs/show_bug.cgi?id=1944 Does this mean that COSS can't be successfully used with FreeBSD 7

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2008-09-11 Thread Amos Jeffries
Mark Powell wrote: On Thu, 14 Aug 2008, Mark Powell wrote: On Thu, 14 Aug 2008, Adrian Chadd wrote: Don't load aio.ko; that way if squid tries using the POSIX AIO routines it'll crash. I should get around to removing those from Squid-2.HEAD (as the implementation isn't "good enough" for the c

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2008-09-11 Thread Mark Powell
On Thu, 14 Aug 2008, Mark Powell wrote: On Thu, 14 Aug 2008, Adrian Chadd wrote: Don't load aio.ko; that way if squid tries using the POSIX AIO routines it'll crash. I should get around to removing those from Squid-2.HEAD (as the implementation isn't "good enough" for the current way Squid doe

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2008-08-14 Thread Mark Powell
On Thu, 14 Aug 2008, Adrian Chadd wrote: Don't load aio.ko; that way if squid tries using the POSIX AIO routines it'll crash. I should get around to removing those from Squid-2.HEAD (as the implementation isn't "good enough" for the current way Squid does disk IO) and reintroduce it later in a

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2008-08-14 Thread Adrian Chadd
Don't load aio.ko; that way if squid tries using the POSIX AIO routines it'll crash. I should get around to removing those from Squid-2.HEAD (as the implementation isn't "good enough" for the current way Squid does disk IO) and reintroduce it later in a more sensibly abstracted disk IO layer. Yes

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2008-08-14 Thread Mark Powell
On Thu, 14 Aug 2008, Adrian Chadd wrote: I'm not sure how much time I'm going to have to look at this code right now. My priorities are elsewhere and you're the only person who is currently reporting this sort of pending relocation issues with COSS and FreeBSD-6.3. I'd suggest patching the sou

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2008-08-13 Thread Adrian Chadd
I'm not sure how much time I'm going to have to look at this code right now. My priorities are elsewhere and you're the only person who is currently reporting this sort of pending relocation issues with COSS and FreeBSD-6.3. I'd suggest patching the source to propagate upward the async IO write f

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2008-08-13 Thread Mark Powell
Hi, Updated to 2.7.STABLE4. Curiosity got the better of me and I re-enabled COSS. The same failure still seems to be occuring i.e. 'storeCossCompletePendingReloc: got failure (-1)' and a segfault on FreeBSD 6.3-p4. Not sure the bug has been looked at since I filed it? http://www.squid-c

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2007-04-26 Thread Adrian Chadd
On Thu, Apr 26, 2007, Mark Powell wrote: > It does stop the crashes, but I'm getting a lot of errors, so of which > appear to be new ones: Very eww. Now we need to figure out why the hell its spitting out those pending relocate IO errors as its probably playing havoc with things. Could you do

Re: [squid-users] COSS causing squid Segment Violation on FreeBSD 6.2S (store_io_coss.c)

2007-04-26 Thread Mark Powell
On Thu, 26 Apr 2007, Adrian Chadd wrote: Change: xmemcpy(p, buf, len); to be: if (errflag == 0) { assert(len >= 0); xmemcpy(p, buf, len); } That should stop the crashes but it won't stop the IO errors and I'm not quite sure whether COSS will return crap to the client request or not. COSS