From: Chris Mason <chris.mason@oracle.com>
To: Luke Sheldrick <luke@sheldrick.co.uk>
Cc: btrfs hackers <linux-btrfs@vger.kernel.org>
Subject: Re: Recovering "parent transid verify failed"
Date: Wed, 23 Mar 2011 20:07:03 -0400 [thread overview]
Message-ID: <1300925154-sup-1589@think> (raw)
In-Reply-To: <8C6E0242B0336C4CB6065C37C0A2A959EB2E550547@londondc02.an0key.net>
Excerpts from Luke Sheldrick's message of 2011-03-23 14:12:45 -0400:
> Hi,
>
> I'm having the same issues as previously mentioned.
>
> Apparently the new fsck tool will be able to recover this?
>
> Few questions, is there a GIT version I can compile and use already for this?
>
> If not, is there any indication of when this will be released?
Yes, I'm still hammering out a reliable way to resolve most of these.
But, please post the messages you're hitting, it is actually a very
generic problem and has many different causes.
What happened to your FS that made them come up?
Which kernel were you running and what was the FS built on top of?
What happens when you grab the latest btrfsck from git and do:
btrfsck -s 1 /dev/xxx
-chris
next prev parent reply other threads:[~2011-03-24 0:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 18:12 Recovering "parent transid verify failed" Luke Sheldrick
2011-03-24 0:07 ` Chris Mason [this message]
[not found] <AANLkTik2t4bG_vwveO=5dovOE=6gDH5FKzjANs7cgRWY@mail.gmail.com>
2011-03-06 10:28 ` Yo'av Moshe
2011-03-06 11:02 ` Hugo Mills
[not found] ` <CAPAyKozRoUaf4OgpdCuc0hNm2fMnON61Z95m1r_QMuHASESyVg@mail.gmail.com>
2012-03-25 12:34 ` Yo'av Moshe
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=1300925154-sup-1589@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=luke@sheldrick.co.uk \
/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).