The issues that we saw only came to light under stress. The
application I am referring to ran under a fair bit of load at the best
of times but it was during sustained spikes that the flaws in our
driver made themselves apparent.
Mind you, we weren't using JFS, so I'm not sure how that would have reacted.
On Mon, May 25, 2009 at 12:19 PM, Per Jessen <per@stripped> wrote:
> Michael Dykman wrote:
>> Given the new hardware, I'm now suspecting the RAID controller. I have
>> seen misconfigured RAIDs or bad RAID drivers take out a server in just
>> such a manner. I had a debian server connected to an EMC SAN.. As
>> debian isn't supported, we had this open-source driver which gave us
>> no end of problems.
>> If a logical drive acts up or does something unexpected, MySQL could
>> react to that in a manner consistent with what you are seeing in your
> Shouldn't/wouldn't the filesystem complain first? There is a lot of
> activity on the filesystem, mysql is just a tiny part of it.
>> I would be tempted to put the hardware through a stress test. I know
>> that's not much help.
> I really have no reason to suspect the hardware. It's new, but it's
> been running in "burn-in" mode for about a month (although not with
> much load, mostly idling). I might as well suspect the mysql build and
> try upgrading to a newer one.
> /Per Jessen, Zürich
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
- michael dykman
- All models are wrong. Some models are useful.