From: Anders Ossowicki <aowi@novozymes.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"aradford@gmail.com" <aradford@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: 2.6.38.8 kernel bug in XFS or megaraid driver with heavy I/O load
Date: Wed, 12 Oct 2011 14:29:33 +0200 [thread overview]
Message-ID: <20111012122933.GA3719@otto.nzcorp.net> (raw)
In-Reply-To: <20111012003526.GI3159@dastard>
On Wed, Oct 12, 2011 at 02:35:26AM +0200, Dave Chinner wrote:
> Memory corruption can be caused by more than just a bad memory
> stick. You've got a brand new driver running your brand new
> controller and it may still have bugs - it might be scribbling over
> memory it doesn't own because of off-by-one index errors, etc. It's
> much more likely that that new hardware or driver code is the cause
> of your problem than an undetected ECC memory error or core VM
> problem.
Ah, now that I agree on. A few more observations from today's experiments:
First of all, there are two MegaRAID controllers in the machine. The
old'n'reliable 8888ELP and the new'n'wonky 9285-8e. Both are using the megaraid
driver and the 8888ELP card ran with the megaraid driver prior to the
refactoring that introduced support for 9285-8e without a hitch for about a
year.
We've gotten to a point where we can reliably reproduce this by running certain
queries in postgresql when data from the disk is cached. E.g
foo=# select count(*) from foo.sequence;
ERROR: invalid page header in block 529134 of relation base/16385/58318945
If we echo 3 >/proc/sys/vm/drop_caches and reload postgres, the same queries
work. This does indeed smell like memory corruption.
The 9285-8e controller has FastPath enabled.
> FWIW, if it's a repeatable problem, you might want to update the
> driver and controller firmware to something more recent and see if
> that solves the problem....
I upgraded the firmware (post-accident) but we're still seeing the corruption.
--
Anders
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-10-12 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111011091757.GA32589@otto.nzcorp.net>
2011-10-11 13:34 ` 2.6.38.8 kernel bug in XFS or megaraid driver with heavy I/O load Christoph Hellwig
2011-10-11 14:13 ` Anders Ossowicki
2011-10-11 16:07 ` Jesper Krogh
2011-10-12 0:35 ` Dave Chinner
2011-10-12 4:13 ` Stan Hoeppner
2011-10-12 12:29 ` Anders Ossowicki [this message]
2011-10-17 12:40 ` jesper
2011-10-24 16:45 ` Michael Monnerie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111012122933.GA3719@otto.nzcorp.net \
--to=aowi@novozymes.com \
--cc=aradford@gmail.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox