From: Christoph Hellwig <hch@infradead.org>
To: "Assarsson, Emil" <Emil.Assarsson@sonyericsson.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: silent corruption after kernel panic?
Date: Mon, 19 Sep 2011 10:27:29 -0400 [thread overview]
Message-ID: <20110919142729.GA20750@infradead.org> (raw)
In-Reply-To: <2BF070A7A2375D46BA1B6087F8D5DCB68BEA722B40@seldmbx01.corpusers.net>
On Mon, Sep 19, 2011 at 02:28:23PM +0200, Assarsson, Emil wrote:
> Hi,
>
> We are running a 20TB XFS filesystem on top of LVM2 and SAN storage (HP
> Open-V) with multipathd. Ubuntu Lucid. The disk write cache is enabled
> and we use mount options rw.
> Sep 16 06:40:34 seldlnx034 kernel: [54607.977261] XFS internal error
> XFS_WANT_CORRUPTED_RETURN at line 381 of
> file /build/buildd/linux-2.6.32/fs/xfs/xfs_alloc.c. Caller
> 0xffffffffa01eed36
> Sep 16 06:40:34 seldlnx034 kernel: [54607.996676] [<ffffffffa0215383>]
> xfs_error_report+0x43/0x50 [xfs]
> Sep 16 06:40:34 seldlnx034 kernel: [54607.996689]
This (corrupted allocation btrees) is a typical indication of missing
cache flushes.
Given that before ~2.6.35 LVM/device mapper was not able to pass through
cache flush requests that is your most likely culprit. A repair will
rebuild the freespace btrees, and make sure to keep the write caches
down the whole stack disabled.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-09-19 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 12:28 silent corruption after kernel panic? Assarsson, Emil
2011-09-19 14:27 ` Christoph Hellwig [this message]
2011-09-23 10:21 ` Assarsson, Emil
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=20110919142729.GA20750@infradead.org \
--to=hch@infradead.org \
--cc=Emil.Assarsson@sonyericsson.com \
--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