From: Anders Ossowicki <aowi@novozymes.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: aradford@gmail.com, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 2.6.38.8 kernel bug in XFS or megaraid driver with heavy I/O load
Date: Tue, 11 Oct 2011 16:13:38 +0200 [thread overview]
Message-ID: <20111011141338.GA11808@otto.nzcorp.net> (raw)
In-Reply-To: <20111011133448.GA10692@infradead.org>
On Tue, Oct 11, 2011 at 03:34:48PM +0200, Christoph Hellwig wrote:
> This is core VM code, and operates purely on on-stack variables except
> for the page cache radix tree nodes / pages. So this either could be a
> core VM bug that no one has noticed yet, or memory corruption. Can you
> run memtest86 on the box?
Unfortunately not, as it is a production server. Pulling it out to memtest 256G
properly would take too long. But it seems unlikely to me that it should be
memory corruption. The machine has been running with the same (ecc) memory for
more than a year and neither the service processor nor the kernel (according to
dmesg) has caught anything before this. It would be a rare (though I admit not
impossible) coincidence if we got catastrophic, undetected memory corruption a
week after attaching a new raid controller with a new disk array.
--
Anders Ossowicki
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-10-11 14:13 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 [this message]
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
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=20111011141338.GA11808@otto.nzcorp.net \
--to=aowi@novozymes.com \
--cc=aradford@gmail.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