From: Christoph Hellwig <hch@infradead.org>
To: Drunkard Zhang <gongfan193@gmail.com>
Cc: Alex Elder <aelder@sgi.com>,
xfs-masters@oss.sgi.com, xfs@oss.sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: bug in xfs: can't recovery metadata log
Date: Tue, 7 Jun 2011 06:32:52 -0400 [thread overview]
Message-ID: <20110607103252.GA15140@infradead.org> (raw)
In-Reply-To: <BANLkTinX_BO94CdQsdmj=atFc-typqr0xg@mail.gmail.com>
On Tue, Jun 07, 2011 at 01:20:23PM +0800, Drunkard Zhang wrote:
> The log recovery failure happened after a hard reboot, I did "mount
> /dev/lg/log /mnt/temp/" twice, but the similar dmesg error.
>
> The xfs lives on LVM, with 4x2TB SATA II disk.
>
> The first time:
> [ 1479.130446] XFS mounting filesystem dm-0
> [ 1479.226525] Starting XFS recovery on filesystem: dm-0 (logdev: internal)
> [ 1506.217842] BUG: unable to handle kernel NULL pointer dereference
> at 00000000000000f8
[...]
> [ 1506.220989] RIP: 0010:[<ffffffff81235f9c>] [<ffffffff81235f9c>]
> xfs_cmn_err+0x6b/0x92
[...]
> [ 1506.226301] [<ffffffff8122922b>] ? kmem_zone_zalloc+0x1f/0x30
> [ 1506.226549] [<ffffffff812098b5>] xfs_error_report+0x39/0x40
> [ 1506.226805] [<ffffffff811e8340>] ? xfs_free_extent+0x8e/0xae
> [ 1506.227056] [<ffffffff811e75cf>] xfs_free_ag_extent+0x3e7/0x70b
> [ 1506.227306] [<ffffffff811e8340>] xfs_free_extent+0x8e/0xae
It looks like you hit one of the XFS_WANT_CORRUPTED_GOTO checks in
xfs_error_report, and we hit something in there that isn't initialized
that early during the mount process. My guess it's actually the
mp->m_fsname dereference in xfs_fs_vcmn_err. It's fixed by the message
rework in 2.6.39+, but that will only prevent the crash, you'll still
get an error and the log recovery will be aborted. If you can get a
more recent kernel on the box I'd be curious what the output form it is.
Did you run older kernels on this machine before? Before 2.6.33 device
mapper support for barriers (aka cache flushes) was incomplete and
frequently led to free space corruption if people left the volatile
write caches on. For MD underneath it event took a bit longer.
If you just want to continue using the filesystem you can nuke the
log using xfs_repair -L.
prev parent reply other threads:[~2011-06-07 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 5:20 bug in xfs: can't recovery metadata log Drunkard Zhang
2011-06-07 6:36 ` Drunkard Zhang
2011-06-07 7:43 ` Michael Monnerie
2011-06-07 7:56 ` Drunkard Zhang
2011-06-07 8:30 ` Michael Monnerie
2011-06-07 10:32 ` Christoph Hellwig [this message]
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=20110607103252.GA15140@infradead.org \
--to=hch@infradead.org \
--cc=aelder@sgi.com \
--cc=gongfan193@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs-masters@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).