linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Kuther <kuther@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Fsck, parent transid verify failed
Date: Thu, 9 Dec 2010 16:21:03 +0000 (UTC)	[thread overview]
Message-ID: <loom.20101209T171330-48@post.gmane.org> (raw)
In-Reply-To: 1291326502-sup-1726@think

Chris Mason <chris.mason <at> oracle.com> writes:

> [...]
> Build the latest tools, then:
> 
> btrfsck -s 1 /dev/xxx
> btrfsck -s 2 /dev/xxx
> 
> If either of these work we have an easy way to get it mounted.  Just let
> me know.
> 

Hello,

I get those "parent transid verify failed" errors too after a system failure.

# btrfsck -s 1 /dev/md0 
using SB copy 1, bytenr 67108864
found 1954912653312 bytes used err is 0
total csum bytes: 1892054684
total tree bytes: 3455627264
total fs tree bytes: 1082691584
btree space waste bytes: 584155173
file data blocks allocated: 12808940421120
 referenced 1933520879616
Btrfs v0.19-35-g1b444cd-dirty
# btrfsck -s 2 /dev/md0 
using SB copy 2, bytenr 274877906944
found 1954912653312 bytes used err is 0
-snip-

Both seem to work.
What would be the steps to get it mounted?

Thanks in advance.

~thomas



  parent reply	other threads:[~2010-12-09 16: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 [this message]
2010-12-10 20:11         ` Chris Mason
2010-12-12 11:21           ` Tom Kuther

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=loom.20101209T171330-48@post.gmane.org \
    --to=kuther@gmx.de \
    --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).