From: Tom Kuther <kuther@gmx.de>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Fsck, parent transid verify failed
Date: Sun, 12 Dec 2010 12:21:27 +0100 [thread overview]
Message-ID: <20101212122127.0befdac2@gimpel.ath.cx> (raw)
In-Reply-To: <1292011722-sup-5780@think>
On Fr, 10.12.10 15:11 Chris Mason <chris.mason@oracle.com> wrote:
> > What would be the steps to get it mounted?
>
> If btrfsck -s is able to find a good super, I've setup a tool that
> will copy the good super over into the default super. It is currently
> sitting in the next branch of the btrfs-progs-unstable repo.
>
> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs-unstable.git
> next
>
> (or git pull into your existing checkout)
>
> Then
>
> make btrfs-select-super
> ./btrfs-selects-super -s 1 /dev/xxx
>
> After this you'll want to do a full backup and make sure things are
> working properly.
>
> -chris
This worked fine. I was able to mount and completely read it.
The volume seems healthy and is fully usable so far.
Thanks a lot!
~thomas
prev parent reply other threads:[~2010-12-12 11:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 11:00 Fsck, parent transid verify failed Tommy Jonsson
2010-12-02 16:21 ` Chris Mason
2010-12-02 21:49 ` Tommy Jonsson
[not found] ` <AANLkTim5-5KQ3_sEb9WY+O1Uj36=3M3i_yQKeuSb7Qe5@mail.gmail.com>
2010-12-02 21:50 ` Chris Mason
2010-12-02 21:59 ` Tommy Jonsson
2010-12-02 22:16 ` Tommy Jonsson
2010-12-08 20:07 ` Tommy Jonsson
2010-12-09 17:14 ` Chris Mason
2010-12-15 12:39 ` Tommy Jonsson
2011-01-03 15:27 ` Tommy Jonsson
2010-12-09 16:21 ` Tom Kuther
2010-12-10 20:11 ` Chris Mason
2010-12-12 11:21 ` Tom Kuther [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=20101212122127.0befdac2@gimpel.ath.cx \
--to=kuther@gmx.de \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
/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).