All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <tch@virtall.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: failed to read log tree, open_ctree failed
Date: Tue, 27 Aug 2013 02:25:09 +0800	[thread overview]
Message-ID: <20130827022509.57de1ab2@virtall.com> (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.


-- 
Tomasz Chmielewski
http://wpkg.org

             reply	other threads:[~2013-08-26 18:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26 18:25 Tomasz Chmielewski [this message]
2013-08-26 18:34 ` failed to read log tree, open_ctree failed Hugo Mills
2013-08-26 18:47   ` Tomasz Chmielewski
2013-08-26 19:01     ` Hugo Mills
2013-08-27  3:56       ` Tomasz Chmielewski

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=20130827022509.57de1ab2@virtall.com \
    --to=tch@virtall.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.