From: Dave Chinner <david@fromorbit.com>
To: Richard Ems <richard.ems@cape-horn-eng.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS (sdd1): Internal error xfs_da_do_buf(2) at line 2097 of file /usr/src/packages/BUILD/kernel-default-3.3.6/linux-3.3/fs/xfs/xfs_da_btree.c.
Date: Tue, 18 Sep 2012 09:49:26 +1000 [thread overview]
Message-ID: <20120917234926.GJ13691@dastard> (raw)
In-Reply-To: <50573A13.7000206@cape-horn-eng.com>
On Mon, Sep 17, 2012 at 04:56:19PM +0200, Richard Ems wrote:
> Hi all,
>
> saturday morning one hard disc on our RAID6 failed. About one hour later,
> the XFS running on that device reported the following error:
>
> XFS (sdd1): Internal error xfs_da_do_buf(2) at line 2097 of file /usr/src/packages/BUILD/kernel-default-3.3.6/linux-3.3/fs/xfs/xfs_da_btree.c.
.....
> Sep 15 07:30:51 fs1 kernel: [7369085.792619] XFS (sdd1): Corruption detected. Unmount and run xfs_repair
>
>
> And this repeating again and again ...
>
> This system has been running fine for 87 days, no power outages or such.
> It's connected to an UPS, and the H800 Raid Controller has a BBU installed.
.....
> Why could this have happened?
Something went wrong at the RAID level (i.e. your hardware) in
handling the disk failure and recovering the array. It corrupted
blocks in the volume rather than recovering them cleanly without
errors. The corrupted blocks happened to be in a directory block,
and a frequently accessed one according to the errors in the log.
What you found in lost+found was the recoverable fragments of the
directory and whatever else was corrupted during the disk failure
incident.
> What more info can I provide to understand this issue and avoid
> this to happen again?
I'd be asking your hardware vendor about why it corrupted the
volume on a single disk failure when it is supposed to be able to
transparently handle double disk failures without losing/corrupting
data.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-09-17 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 14:56 XFS (sdd1): Internal error xfs_da_do_buf(2) at line 2097 of file /usr/src/packages/BUILD/kernel-default-3.3.6/linux-3.3/fs/xfs/xfs_da_btree.c Richard Ems
2012-09-17 23:49 ` Dave Chinner [this message]
2012-09-18 8:31 ` Richard Ems
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=20120917234926.GJ13691@dastard \
--to=david@fromorbit.com \
--cc=richard.ems@cape-horn-eng.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