From: Christoph Hellwig <hch@infradead.org>
To: Gregory Farnum <gregory.farnum@dreamhost.com>
Cc: sandeen@sandeen.net, xfs@oss.sgi.com
Subject: Re: EFSCORRUPTED on mount?
Date: Tue, 22 Nov 2011 17:11:50 -0500 [thread overview]
Message-ID: <20111122221150.GA21028@infradead.org> (raw)
In-Reply-To: <CAF3hT9Cu+56WJqzHVu+fMgquddwoMsfW-WC8CvRRBtC4PA3uHw@mail.gmail.com>
On Tue, Nov 22, 2011 at 10:47:24AM -0800, Gregory Farnum wrote:
> Barriers on (at least, nobody turned them off); the RAID card is
> battery-backed; here are megacli dumps:
> http://pastebin.com/yTskgzWG
> http://pastebin.com/ekhczycy
I had a lot of of issues with megaraid cards and their unsafe caching
settings, up to the point that I'd recommend staying away from them
now. Can you check in the megacli config if the _disk_ write caches
are enabled? megaraid adapters used to do that a lot, and given that
the disk cache isn't batter backed it's fairly fatal.
I think in your dump this one might be the culprit given that SATA
disks outside of a few niches come with a writeback cache policy:
Disk Cache Policy: Disk's Default
try changing that to an explicit writethrough mode - and maybe try
running a crash data integrity test like
http://www.complang.tuwien.ac.at/anton/hdtest/
on this controller.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-22 22:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 18:06 EFSCORRUPTED on mount? Gregory Farnum
2011-11-21 21:52 ` Emmanuel Florac
2011-11-21 22:13 ` Ben Myers
2011-11-22 0:21 ` Gregory Farnum
2011-11-22 1:41 ` Dave Chinner
2011-11-22 18:47 ` Gregory Farnum
2011-11-22 18:52 ` Eric Sandeen
2011-11-22 19:29 ` Gregory Farnum
2011-11-22 21:53 ` Eric Sandeen
2011-11-22 22:55 ` Christoph Hellwig
2011-11-23 0:03 ` Gregory Farnum
2011-11-23 15:51 ` Christoph Hellwig
2011-11-22 22:11 ` Christoph Hellwig [this message]
2011-11-22 8:06 ` Emmanuel Florac
2011-11-22 15:06 ` Eric Sandeen
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=20111122221150.GA21028@infradead.org \
--to=hch@infradead.org \
--cc=gregory.farnum@dreamhost.com \
--cc=sandeen@sandeen.net \
--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