Skip to contentSkip to conversation

failed to read log tree, open_ctree failed

DISCUSSION Tomasz Chmielewski 2 participants 5 messages Aug 26, 2013 – Aug 27, 2013 Btrfs file system

lore
Share & tools
lore
#0 lore raw

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.

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#1 lore raw
Quoted 17 lines · 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
Quoted 4 lines

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.

Signature · 4 lines
=== 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.                        
#2 lore raw
Quoted 7 lines · On Mon, 26 Aug 2013 19:34:19 +0100 Hugo Mills <[email protected]> wrote:
Quoted 7 lines

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

Quoted 6 lines
Quoted 4 lines

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?

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#3 lore raw
Quoted 12 lines · Tomasz Chmielewski
Quoted 9 lines · On Mon, 26 Aug 2013 19:34:19 +0100 Hugo Mills <[email protected]> wrote:
Quoted 9 lines

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.

Quoted 8 lines
Quoted 4 lines
Quoted 2 lines

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.

Signature · 4 lines
=== 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.                        
#4 lore raw
Quoted 6 lines · On Mon, 26 Aug 2013 20:01:46 +0100 Hugo Mills <[email protected]> wrote:
Quoted 1 line

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.

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org