failed to read log tree, open_ctree failed

failed to read log tree, open_ctree failed

[Tomasz Chmielewski]

I had a RAID-1 btrfs filesystem with Linux 3.10.

After hard reset, I'm no longer able to mount it:

[   35.254122] Btrfs loaded
[   35.254577] device label test-btrfs devid 1 transid 97966 /dev/sda4
[   35.254819] device label test-btrfs devid 3 transid 97966 /dev/sdb4
[   35.255032] device label test-btrfs devid 3 transid 97966 /dev/sdb4
[   35.255552] btrfs: force zlib compression
[   35.255645] btrfs: disk space caching is enabled
[   35.379806] btrfs: bdev /dev/sda4 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0
[   56.209412] parent transid verify failed on 3321036099584 wanted 97967 found 97966
[   56.225990] parent transid verify failed on 3321036099584 wanted 97967 found 97966
[   56.226128] btrfs: failed to read log tree
[   56.344483] btrfs: open_ctree failed


I've tried with 3.11-rc7, but it gives the same result.

Any hints how to recover from that?
I have backups, but it would be nice if the filesystem just mounted.


-- 
Tomasz Chmielewski
http://wpkg.org

Re: failed to read log tree, open_ctree failed

[Hugo Mills]

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

On Tue, Aug 27, 2013 at 02:25:09AM +0800, Tomasz Chmielewski wrote:
> I had a RAID-1 btrfs filesystem with Linux 3.10.
> 
> After hard reset, I'm no longer able to mount it:
> 
> [   35.254122] Btrfs loaded
> [   35.254577] device label test-btrfs devid 1 transid 97966 /dev/sda4
> [   35.254819] device label test-btrfs devid 3 transid 97966 /dev/sdb4
> [   35.255032] device label test-btrfs devid 3 transid 97966 /dev/sdb4
> [   35.255552] btrfs: force zlib compression
> [   35.255645] btrfs: disk space caching is enabled
> [   35.379806] btrfs: bdev /dev/sda4 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0
> [   56.209412] parent transid verify failed on 3321036099584 wanted 97967 found 97966
> [   56.225990] parent transid verify failed on 3321036099584 wanted 97967 found 97966
> [   56.226128] btrfs: failed to read log tree
> [   56.344483] btrfs: open_ctree failed
> 
> 
> I've tried with 3.11-rc7, but it gives the same result.
> 
> Any hints how to recover from that?
> I have backups, but it would be nice if the filesystem just mounted.

   Try mounting with both -orecovery and -oro,recovery.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
              --- Python is executable pseudocode; perl ---              
                        is executable line-noise.                        

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

Re: failed to read log tree, open_ctree failed

[Tomasz Chmielewski]

On Mon, 26 Aug 2013 19:34:19 +0100
Hugo Mills <hugo@carfax.org.uk> wrote:

> > corrupt 0, gen 0 [   56.209412] parent transid verify failed on
> > 3321036099584 wanted 97967 found 97966 [   56.225990] parent
> > transid verify failed on 3321036099584 wanted 97967 found 97966
> > [   56.226128] btrfs: failed to read log tree [   56.344483] btrfs:
> > open_ctree failed
> > 
> > 
> > I've tried with 3.11-rc7, but it gives the same result.
> > 
> > Any hints how to recover from that?
> > I have backups, but it would be nice if the filesystem just mounted.
> 
>    Try mounting with both -orecovery and -oro,recovery.

Neither worked, same error.

Anything else I can try?

-- 
Tomasz Chmielewski
http://wpkg.org

Re: failed to read log tree, open_ctree failed

[Hugo Mills]

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

On Tue, Aug 27, 2013 at 02:47:48AM +0800, Tomasz Chmielewski wrote:
> On Mon, 26 Aug 2013 19:34:19 +0100
> Hugo Mills <hugo@carfax.org.uk> wrote:
> 
> > > corrupt 0, gen 0 [   56.209412] parent transid verify failed on
> > > 3321036099584 wanted 97967 found 97966 [   56.225990] parent
> > > transid verify failed on 3321036099584 wanted 97967 found 97966
> > > [   56.226128] btrfs: failed to read log tree [   56.344483] btrfs:
> > > open_ctree failed
> > > 
> > > 
> > > I've tried with 3.11-rc7, but it gives the same result.
> > > 
> > > Any hints how to recover from that?
> > > I have backups, but it would be nice if the filesystem just mounted.
> > 
> >    Try mounting with both -orecovery and -oro,recovery.
> 
> Neither worked, same error.
> 
> Anything else I can try?

   Oh, hang on... that's the log tree.

   btrfs-zero-log may help. If you can take a btrfs-image of the
filesystem before running that, josef would like to see it.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
              --- Python is executable pseudocode; perl ---              
                        is executable line-noise.                        

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

Re: failed to read log tree, open_ctree failed

[Tomasz Chmielewski]

On Mon, 26 Aug 2013 20:01:46 +0100
Hugo Mills <hugo@carfax.org.uk> wrote:

> > Anything else I can try?
> 
>    Oh, hang on... that's the log tree.
> 
>    btrfs-zero-log may help. If you can take a btrfs-image of the
> filesystem before running that, josef would like to see it.

btrfs-zero-log did the trick, thanks.

-- 
Tomasz Chmielewski
http://wpkg.org