From: Tommy Jonsson <quazzie@gmail.com>
To: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: Fsck, parent transid verify failed
Date: Thu, 2 Dec 2010 23:16:25 +0100 [thread overview]
Message-ID: <AANLkTimEHf9tohZ8ZkOiZ-CfTkNgumAFVMsm_FSP9M7S@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=TQ5FeVH2=56kNrdiUNBmSc=dSOwMwcKOVkaTq@mail.gmail.com>
Tried "btrfs-debug-tree /dev/sda" and "btrfs-debug-tree -e /dev/sda" :
parent transid verify failed on 2721514774528 wanted 39651 found 39649
btrfs-debug-tree: disk-io.c:739: open_ctree_fd: Assertion
`!(!tree_root->node)' failed.
dmesg said:
[268375.903581] device fsid 734a485d12c77872-9b0b5aa408670db4 devid 2
transid 39650 /dev/sdd
[268375.904241] device fsid 734a485d12c77872-9b0b5aa408670db4 devid 1
transid 39651 /dev/sdc
[268375.904526] device fsid 734a485d12c77872-9b0b5aa408670db4 devid 3
transid 39651 /dev/sda
-tommy
On Thu, Dec 2, 2010 at 10:59 PM, Tommy Jonsson <quazzie@gmail.com> wrot=
e:
> $ btrfsck -s 1 /dev/sda
> using SB copy 1, bytenr 67108864
> parent transid verify failed on 2721514774528 wanted 39651 found 3964=
9
> btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->node)=
' failed.
> Aborted
>
> $ btrfsck -s 2 /dev/sda
> using SB copy 2, bytenr 274877906944
> parent transid verify failed on 2721514774528 wanted 39651 found 3964=
9
> btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->node)=
' failed.
> Aborted
>
> -tommy
>
>
> On Thu, Dec 2, 2010 at 10:50 PM, Chris Mason <chris.mason@oracle.com>=
wrote:
>> Excerpts from Tommy Jonsson's message of 2010-12-02 16:45:39 -0500:
>>> I can't remember if i used -m raid0.
>>> I think i just used "mkfs.btrfs /dev/sda" then "btrfs device add /d=
ev/sdb"
>>> and same for sdc.
>>> I am sure that i didn't explicitly use -m raid1 or raid10.
>>> Is there a way that i can check this ?
>>
>> The defaults will maintain raid1 as you add more drives. =A0We can c=
heck
>> it with btrfs-debug-tree from the git repository. =A0But, more below=
=2E
>>
>>>
>>> If i do have raid0 for both metadata and data is there anything i c=
an do ?
>>> I've been looking at the source but haven't got my head around it y=
et.
>>>
>>> What whould happen if i just ignore/bypass the transid error?
>>>
>>> The error:
>>> [265889.197279] device fsid 734a485d12c77872-9b0b5aa408670db4 devid=
3
>>> transid 39651 /dev/sda
>>> [265889.198266] btrfs: use compression
>>> [265889.647817] parent transid verify failed on 2721514774528 wante=
d 39651
>>> found 39649
>>> [265889.672632] btrfs: open_ctree failed
>>>
>>> Or could i update the metadata to want 39649 ?
>>
>> The first thing I would try is:
>>
>> git pull git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-p=
rogs-unstable.git
>>
>> 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. =A0Ju=
st let
>> me know.
>>
>> -chris
>>
>
--
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-02 22:16 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 [this message]
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
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=AANLkTimEHf9tohZ8ZkOiZ-CfTkNgumAFVMsm_FSP9M7S@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).