From: Tommy Jonsson <quazzie@gmail.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Fsck, parent transid verify failed
Date: Wed, 15 Dec 2010 13:39:54 +0100 [thread overview]
Message-ID: <AANLkTik5SQeH1ZZcbiPbYLL9Dghsp93-zvciiVCGCkVM@mail.gmail.com> (raw)
In-Reply-To: <1291914789-sup-96@think>
> Excerpts from Tommy Jonsson's message of 2010-12-08 15:07:58 -0500:
>> >> 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. =A0=
Just let
>> >> me know.
>> >>
>> >> -chris
>> >>
>>
>> > $ btrfsck -s 1 /dev/sda
>> > using SB copy 1, bytenr 67108864
>> > parent transid verify failed on 2721514774528 wanted 39651 found 3=
9649
>> > btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->no=
de)' failed.
>> > Aborted
>> >
>> > $ btrfsck -s 2 /dev/sda
>> > using SB copy 2, bytenr 274877906944
>> > parent transid verify failed on 2721514774528 wanted 39651 found 3=
9649
>> > btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->no=
de)' failed.
>> > Aborted
>> >
>> > Tried "btrfs-debug-tree /dev/sda" and "btrfs-debug-tree -e /dev/sd=
a" :
>> > parent transid verify failed on 2721514774528 wanted 39651 found 3=
9649
>> > btrfs-debug-tree: disk-io.c:739: open_ctree_fd: Assertion
>> > `!(!tree_root->node)' failed.
>> >
>> > dmesg said:
>> > [268375.903581] device fsid 734a485d12c77872-9b0b5aa408670db4 devi=
d 2 transid 39650 /dev/sdd
>> > [268375.904241] device fsid 734a485d12c77872-9b0b5aa408670db4 devi=
d 1 transid 39651 /dev/sdc
>> > [268375.904526] device fsid 734a485d12c77872-9b0b5aa408670db4 devi=
d 3 transid 39651 /dev/sda
>>
>> Sorry to be a bother, but do you have any other suggestions ?
>
> Not a bother at all, I'm polishing off a version of fsck that I hope
> will be able to construct a good tree for you. =A0It's my main priori=
ty
> right now and I hope to have something ready early Monday.
>
> -chris
>
Hi Chris.
Thanks for all your help. Any progress on the fsck ?
I pulled the latest btrfs-progs-unstable and recompiled, same output
from all the commands (btrfsck -s / btrfs-debug-tree).
-tommy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-12-15 12:39 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 [this message]
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
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=AANLkTik5SQeH1ZZcbiPbYLL9Dghsp93-zvciiVCGCkVM@mail.gmail.com \
--to=quazzie@gmail.com \
--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).