Marc-Christian Petersen wrote:
> On Thursday 11 April 2002 13:56, Marc Elsen wrote:
>> Hmm, I believe that the original poster's problem should >at
>> least< be verified on another system with EXT3 before SQUID is
>> blamed. I mean more exactly : before it can be claimed that SQUID would
>> have tricked a bug in EXT3; which has an app. can never be
>> excluded, that is true. Programs have been know to crash os-es
>> too...
>
> Yes, you are right. I forgot to test it on another system :(
>
> Now i have another clean system i can test it with. Stay tuned for a
> report, i think i have the results this evening.
You'll probably still hit it. I was able to reliably reproduce a kernel
oops when I was benchmarking various Squid revisions a few weeks back on
ext3 and ReiserFS. I was able to hit it with Squid 2.4.STABLE4, which
you've said hasn't happened for you.
I had no similar problems about 6 months ago when testing ext3 with
Squid 2.4.STABLE1, or thereabouts....but I suspect a bug has crept into
ext3--not into Squid (though bugs do creep into Squid too...I haven't
had any problems with my ReiserFS systems, and I've got a ton of those
performing reliably with STABLE6).
Interestingly, the local test machine that I was browsing through when
this thread first started up (which is running STABLE6 on ext3) stopped
responding. Sure enough, kernel oops.
I would trust a production Squid to an ext3 FS at this point. ReiserFS
and ext2 have proven much more stable.
-- Joe Cooper <joe@swelltech.com> http://www.swelltech.com Web Caching Appliances and SupportReceived on Thu Apr 11 2002 - 06:42:43 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:07:31 MST