From: Richard Ems <richard.ems@cape-horn-eng.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair v3.1.6 - Segmentation fault AND XFS internal error xfs_btree_check_sblock
Date: Tue, 18 Oct 2011 11:58:59 +0200 [thread overview]
Message-ID: <4E9D4DE3.5080304@cape-horn-eng.com> (raw)
In-Reply-To: <20111017225223.GU3159@dastard>
On 10/18/2011 12:52 AM, Dave Chinner wrote:
> A corrupt inode allocation btree - not a particularly common type of
> corruption to be reported. Do you know what caused the errors to
> start being reported? A crash, a bad disk, a raid rebuild, something
> else? That information always helps us understand how badly damaged
> the filesystem might be....
We had a hard disc failure on an Areca 1680 RAID controller, RAID 6. I
checked the firmware and the last available version is already installed.
> And I'd guess that is failing on a different problem - a corrupt
> inode most likely. You've build xfs-repair from the source code -
> can yo urun it under gdb so we can see where it is dying?
I already run it under gdb and sent some mails to Christoph Hellwig. He
found an *issue* in the xfsprogs/repair/attr_repair.c code and sent me a
patch that fixed it. Now "xfs_repair -n -P /dev/sdb1" runs without
errors. But before repairing the XFS I have to rsync as much as I can
from this XFS to another one which is still not available. So it will
take a couple of days before I can run xfs_repair on the XFS.
> That sounds like there's a *lot* of damage to the filesystem. That
> makes it even more important that we understand what caused the
> damage in the first place....
Yes, lots of damage. 8(
Thanks for your help,
Richard
--
Richard Ems mail: Richard.Ems@Cape-Horn-Eng.com
Cape Horn Engineering S.L.
C/ Dr. J.J. Dómine 1, 5º piso
46011 Valencia
Tel : +34 96 3242923 / Fax 924
http://www.cape-horn-eng.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-10-18 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 14:42 xfs_repair v3.1.6 - Segmentation fault AND XFS internal error xfs_btree_check_sblock Richard Ems
2011-10-17 15:02 ` Christoph Hellwig
2011-10-17 15:08 ` Richard Ems
2011-10-17 22:52 ` Dave Chinner
2011-10-18 9:58 ` Richard Ems [this message]
2011-10-24 16:55 ` 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=4E9D4DE3.5080304@cape-horn-eng.com \
--to=richard.ems@cape-horn-eng.com \
--cc=david@fromorbit.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