Fsck, parent transid verify failed

Fsck, parent transid verify failed

[Tommy Jonsson]

Hi folks!

Been using btrfs for quite a while now, worked great until now. 
Got power-loss on my machine and now i have the "parent transid verify
failed on X wanted X found X" problem.
So I can't get it to mount.

My btrfs is spread over sda (2tb), sdc(2tb), sdd(1tb).

Is this something that an offline fsck could fix ? 
If so is the fsck-util being developed ?
Is there a way to mount the FS in a read-only mode or something to rescue
the data ?

Thanks, Tommy.

Re: Fsck, parent transid verify failed

[Chris Mason]

Excerpts from Tommy Jonsson's message of 2010-12-01 06:00:56 -0500:
> Hi folks!
> 
> Been using btrfs for quite a while now, worked great until now. 
> Got power-loss on my machine and now i have the "parent transid verify
> failed on X wanted X found X" problem.
> So I can't get it to mount.
> 
> My btrfs is spread over sda (2tb), sdc(2tb), sdd(1tb).
> 
> Is this something that an offline fsck could fix ? 
> If so is the fsck-util being developed ?
> Is there a way to mount the FS in a read-only mode or something to rescue
> the data ?

Which kernel are you on?  Unless you formatted with -m raid0, the
current git tree should be able to read this FS by using the second copy
of the metadata.

-chris

Re: Fsck, parent transid verify failed

[Tommy Jonsson]

I'm on kernel 2.6.35

I can't remember if i used -m raid0.
I think i just used "mkfs.btrfs /dev/sda" then "btrfs device add
/dev/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 ?

If i do have raid0 for both metadata and data is there anything i can d=
o ?
I've been looking at the source but haven't got my head around it yet.

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 wanted
39651 found 39649
[265889.672632] btrfs: open_ctree failed

Or could i update the metadata to want 39649 ?

Thanks again!

On Thu, Dec 2, 2010 at 5:21 PM, Chris Mason <chris.mason@oracle.com> wr=
ote:
>
> Excerpts from Tommy Jonsson's message of 2010-12-01 06:00:56 -0500:
> > Hi folks!
> >
> > Been using btrfs for quite a while now, worked great until now.
> > Got power-loss on my machine and now i have the "parent transid ver=
ify
> > failed on X wanted X found X" problem.
> > So I can't get it to mount.
> >
> > My btrfs is spread over sda (2tb), sdc(2tb), sdd(1tb).
> >
> > Is this something that an offline fsck could fix ?
> > If so is the fsck-util being developed ?
> > Is there a way to mount the FS in a read-only mode or something to =
rescue
> > the data ?
>
> Which kernel are you on? =A0Unless you formatted with -m raid0, the
> current git tree should be able to read this FS by using the second c=
opy
> of the metadata.
>
> -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

Re: Fsck, parent transid verify failed

[Chris Mason]

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 /dev/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.  We can check
it with btrfs-debug-tree from the git repository.  But, more below.

> 
> If i do have raid0 for both metadata and data is there anything i can do ?
> I've been looking at the source but haven't got my head around it yet.
> 
> 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 wanted 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-progs-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.  Just let
me know.

-chris

Re: Fsck, parent transid verify failed

[Tommy Jonsson]

$ btrfsck -s 1 /dev/sda
using SB copy 1, bytenr 67108864
parent transid verify failed on 2721514774528 wanted 39651 found 39649
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 39649
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> w=
rote:
> 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 /de=
v/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 ch=
eck
> it with btrfs-debug-tree from the git repository. =A0But, more below.
>
>>
>> If i do have raid0 for both metadata and data is there anything i ca=
n do ?
>> I've been looking at the source but haven't got my head around it ye=
t.
>>
>> 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 wanted=
 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-pr=
ogs-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. =A0Jus=
t 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

Re: Fsck, parent transid verify failed

[Tommy Jonsson]

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

Re: Fsck, parent transid verify failed

[Tommy Jonsson]

>> 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.
>>
>> -chris
>>

> $ btrfsck -s 1 /dev/sda
> using SB copy 1, bytenr 67108864
> parent transid verify failed on 2721514774528 wanted 39651 found 39649
> 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 39649
> btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->node)' failed.
> Aborted
>
> 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

Sorry to be a bother, but do you have any other suggestions ?

Thanks!

-tommy

Re: Fsck, parent transid verify failed

[Chris Mason]

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.  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 39649
> > 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 39649
> > btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->node)' failed.
> > Aborted
> >
> > 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
> 
> 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.  It's my main priority
right now and I hope to have something ready early Monday.

-chris

Re: Fsck, parent transid verify failed

[Tommy Jonsson]

> 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

Re: Fsck, parent transid verify failed

[Tommy Jonsson]

On Thu, Dec 9, 2010 at 6:14 PM, Chris Mason <chris.mason@oracle.com> wr=
ote:
> 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 again Chris.
Hope you survived Christmas and new year :]

Just wanted to check in and see how you are progressing on the btrfsck?
Drop me a mail if you want me to test/debug anything.

-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

Re: Fsck, parent transid verify failed

[Tom Kuther]

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

Re: Fsck, parent transid verify failed

[Chris Mason]

Excerpts from Tom Kuther's message of 2010-12-09 11:21:03 -0500:
> 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?

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

Re: Fsck, parent transid verify failed

[Tom Kuther]

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