Recovering "parent transid verify failed"

Recovering "parent transid verify failed"

[Yo'av Moshe]

Hey,
I'd start by saying that I know Btrfs is a still experimental, and so
there's no guarantee that one would be able to help me at all... But I
thought I'll try anyway :-)

Few months ago I bought a new laptop and installed ArchLinux on it,
with Btrfs on the root filesystem... I know, it's not the smartest
thing to do...
After a few month I had issues with my hibernations scripts, and one
day I tried to hibernate my computer but it didn't go that well, and,
well, ever since then my Btrfs partition is not accessible.
I opened up the Btrfs FAQ and saw that the fsck tool should be out by
the end of 2010, and thought "oh well, I could wait until then", and
went on and installed Ubuntu with Ext4 on another small partition.

But times goes one and the fsck tool is still in development... I've
tried using the code from GIT and it didn't work, and I'm starting to
wonder (a) if there's any hope at all and (b) what other step am I
able to do to recover my old Btrfs partition.

When trying to mount the Btrfs parition I get this in dmesg:
[105252.779080] device fsid d14e78a602757297-bf762d859b406ca9 devid 1
transid 135714 /dev/sda4
[105252.818697] parent transid verify failed on 216925220864 wanted
135714 found 135713
[105252.819599] parent transid verify failed on 216925220864 wanted
135714 found 135713
[105252.822598] parent transid verify failed on 216925220864 wanted
135714 found 135713
[105252.974588] btrfs: open_ctree failed

This is what I've tried so far:

> btrfs-select-super
>> -s 1 gives me this error:
using SB copy 1, bytenr 67108864
parent transid verify failed on 216925220864 wanted 135714 found 135713
parent transid verify failed on 216925220864 wanted 135714 found 135713
parent transid verify failed on 216925220864 wanted 135714 found 135713
btrfs-select-super: disk-io.c:739: open_ctree_fd: Assertion
`!(!tree_root->node)' failed.
>> -s 2 gives me this error:
using SB copy 2, bytenr 274877906944
No valid Btrfs found on /dev/sda4

> btrfsck
parent transid verify failed on 216925220864 wanted 135714 found 135713
parent transid verify failed on 216925220864 wanted 135714 found 135713
parent transid verify failed on 216925220864 wanted 135714 found 135713
btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->node)' failed.

Should I wait for btrfsck to be ready?
Am I not using it correctly now?
Is there anyway to recover this partition or should I just wipe it and
reinstall Btrfs only when I'm supposed to?..

Your help is appreciated.

--
Yo'av Moshe

Re: Recovering "parent transid verify failed"

[Hugo Mills]

[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]

On Sun, Mar 06, 2011 at 12:28:41PM +0200, Yo'av Moshe wrote:
> Hey,
> I'd start by saying that I know Btrfs is a still experimental, and so
> there's no guarantee that one would be able to help me at all... But I
> thought I'll try anyway :-)
> 
> Few months ago I bought a new laptop and installed ArchLinux on it,
> with Btrfs on the root filesystem... I know, it's not the smartest
> thing to do...
> After a few month I had issues with my hibernations scripts, and one
> day I tried to hibernate my computer but it didn't go that well, and,
> well, ever since then my Btrfs partition is not accessible.
> I opened up the Btrfs FAQ and saw that the fsck tool should be out by
> the end of 2010, and thought "oh well, I could wait until then", and
> went on and installed Ubuntu with Ext4 on another small partition.
> 
> But times goes one and the fsck tool is still in development... I've
> tried using the code from GIT and it didn't work, and I'm starting to
> wonder (a) if there's any hope at all and (b) what other step am I
> able to do to recover my old Btrfs partition.

   Yes, there is hope. This error should be fixable with the new fsck.

> When trying to mount the Btrfs parition I get this in dmesg:
> [105252.779080] device fsid d14e78a602757297-bf762d859b406ca9 devid 1
> transid 135714 /dev/sda4
> [105252.818697] parent transid verify failed on 216925220864 wanted
> 135714 found 135713
[snip]
> Should I wait for btrfsck to be ready?

   Yes.

> Am I not using it correctly now?

   No, there's not a lot the current version can do right now.

> Is there anyway to recover this partition or should I just wipe it and
> reinstall Btrfs only when I'm supposed to?..
> 
> Your help is appreciated.

   HTH,
   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
     --- "I am the author. You are the audience. I outrank you!" ---     

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

Recovering "parent transid verify failed"

[Luke Sheldrick]

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?

---
Luke Sheldrick
e: luke@sheldrick.co.uk
p: 07880 725099

Re: Recovering "parent transid verify failed"

[Chris Mason]

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

Re: Recovering "parent transid verify failed"

[Yo'av Moshe]

Anything new? I'm still trying to fix my FS every once in a while,
none of the tools helps.


 This is what find-root gives:=C2=A0http://pastebin.com/KycgzhaP

 Btrfsck still only gives this:
 # sudo ./btrfsck --repair /dev/sda4
 enabling repair mode
 parent transid verify failed on 216925220864 wanted 135714 found 13571=
3
 parent transid verify failed on 216925220864 wanted 135714 found 13571=
3
 parent transid verify failed on 216925220864 wanted 135714 found 13571=
3
 parent transid verify failed on 216925220864 wanted 135714 found 13571=
3
 Ignoring transid failure
 btrfsck: root-tree.c:46: btrfs_find_last_root: Assertion
`!(path->slots[0] =3D=3D 0)' failed.

 Anymore details I can give you which will help resolving this? Thanks.

 Yo'av

> =D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A 6 =D7=91=D7=9E=D7=A8=D7=A5 2011 =
11:02, =D7=9E=D7=90=D7=AA Hugo Mills <hugo-lkml@carfax.org.uk>:
>>
>> On Sun, Mar 06, 2011 at 12:28:41PM +0200, Yo'av Moshe wrote:
>> > Hey,
>> > I'd start by saying that I know Btrfs is a still experimental, and=
 so
>> > there's no guarantee that one would be able to help me at all... B=
ut I
>> > thought I'll try anyway :-)
>> >
>> > Few months ago I bought a new laptop and installed ArchLinux on it=
,
>> > with Btrfs on the root filesystem... I know, it's not the smartest
>> > thing to do...
>> > After a few month I had issues with my hibernations scripts, and o=
ne
>> > day I tried to hibernate my computer but it didn't go that well, a=
nd,
>> > well, ever since then my Btrfs partition is not accessible.
>> > I opened up the Btrfs FAQ and saw that the fsck tool should be out=
 by
>> > the end of 2010, and thought "oh well, I could wait until then", a=
nd
>> > went on and installed Ubuntu with Ext4 on another small partition.
>> >
>> > But times goes one and the fsck tool is still in development... I'=
ve
>> > tried using the code from GIT and it didn't work, and I'm starting=
 to
>> > wonder (a) if there's any hope at all and (b) what other step am I
>> > able to do to recover my old Btrfs partition.
>>
>> =C2=A0 Yes, there is hope. This error should be fixable with the new=
 fsck.
>>
>> > When trying to mount the Btrfs parition I get this in dmesg:
>> > [105252.779080] device fsid d14e78a602757297-bf762d859b406ca9 devi=
d 1
>> > transid 135714 /dev/sda4
>> > [105252.818697] parent transid verify failed on 216925220864 wante=
d
>> > 135714 found 135713
>> [snip]
>> > Should I wait for btrfsck to be ready?
>>
>> =C2=A0 Yes.
>>
>> > Am I not using it correctly now?
>>
>> =C2=A0 No, there's not a lot the current version can do right now.
>>
>> > Is there anyway to recover this partition or should I just wipe it=
 and
>> > reinstall Btrfs only when I'm supposed to?..
>> >
>> > Your help is appreciated.
>>
>> =C2=A0 HTH,
>> =C2=A0 Hugo.
>>
>> --
>> =3D=3D=3D Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug=
=2Eorg.uk =3D=3D=3D
>> =C2=A0PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax=
=2Eorg.uk
>> =C2=A0 =C2=A0 --- "I am the author. You are the audience. I outrank =
you!" ---
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.10 (GNU/Linux)
>>
>> iD8DBQFNc2nhIKyzvlFcI40RAsq2AKCrSZE6nXYIRbxfLThwIH/yEeO/iACggwHZ
>> vXj/K5R746xiMj8x6Ehdzbs=3D
>> =3Dzinf
>> -----END PGP SIGNATURE-----
>>
>
>
>
> --
> Yo'av Moshe



--
Yo'av Moshe
--
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