From: Dave Chinner <david@fromorbit.com>
To: David Lechner <david@lechnology.com>
Cc: xfs@oss.sgi.com
Subject: Re: recovering corrupt filesystem after raid failure
Date: Mon, 22 Feb 2016 13:24:39 +1100 [thread overview]
Message-ID: <20160222022439.GE14668@dastard> (raw)
In-Reply-To: <56CA6492.7000407@lechnology.com>
On Sun, Feb 21, 2016 at 07:29:54PM -0600, David Lechner wrote:
> Long story short, I had a dual disk failure in a raid 5. I've managed to
> get the raid back up and salvaged what I could. However, the xfs is
> seriously damaged. I've tried running xfs_repair, but it is failing and
> it recommended to send a message to this mailing list. This is an Ubuntu
> 12.04 machine, so xfs_repair version 3.1.7.
So the first thing to do is get a more recent xfsprogs package and
try that. There's not a lot of point in us looking at problems with
a 4 and half year old package that we've probably already fixed.
> The file system won't mount. Fails with "mount: Structure needs
> cleaning". So I tried xfs_repair. I had to resort to xfs_repair -L
> because the first 500MB or so of the filesystem was wiped out.
Oh, so even if you can repair the filesystem, your data is likely to
be irretreivably corrupted.
> Now,
> xfs_repair /dev/md127 gets stuck, so I am running xfs_repair -P
> /dev/md127. This gets much farther, but it is failing too. It gives an
> error message like this:
>
>
> ...
> disconnected inode 2101958, moving to lost+found
> corrupt dinode 2101958, extent total = 1, nblocks = 0. This is a bug.
> Please capture the filesystem metadata with xfs_metadump and
> report it to xfs@oss.sgi.com.
> cache_node_purge: refcount was 1, not zero (node=0x7f2c57e1b120)
>
> fatal error -- 117 - couldn't iget disconnected inode
>
>
>
> However, nblocks = 0 does not seem to be true...
Probably because it got cleared in memory before this problem was
tripped over.
> If I re-run xfs_repair -P /dev/md127, it will fail on different
> seemingly random inode with the same error message.
Yup, you definitely need to run a current xfs_repair on this
filesystem before going any further.
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:[~2016-02-22 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 1:29 recovering corrupt filesystem after raid failure David Lechner
2016-02-22 2:24 ` Dave Chinner [this message]
2016-02-22 17:53 ` David Lechner
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=20160222022439.GE14668@dastard \
--to=david@fromorbit.com \
--cc=david@lechnology.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