All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: Robert White <rwhite@pobox.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Check tree block failed, want=17716610236416, have=0
Date: Thu, 23 Oct 2014 22:05:50 -0400	[thread overview]
Message-ID: <20141024020545.GD17380@hungrycats.org> (raw)
In-Reply-To: <20141024012448.GC17380@hungrycats.org>

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

On Thu, Oct 23, 2014 at 09:24:48PM -0400, Zygo Blaxell wrote:
> On Thu, Oct 23, 2014 at 05:28:58PM -0700, Robert White wrote:
> > You may be in deep error land from the long use of 3.10... that
> > said, the --init-csum-tree or --init-extent-tree options may be your
> > friend here. The backtrace shows you are in "open_ctree" so the
> > former is more likely the better bet.

Alas, both fail:

	# btrfs check --repair --init-csum-tree --init-extent-tree /dev/mapper/md15
	enabling repair mode
	Creating a new CRC tree
	Couldn't open file system

Same result with each option individually, except that when
--init-csum-tree is absent, so is the "Creating a new CRC tree" message.

I'm also trying 'btrfs rescue chunk-recover -v' but so far it has read
many gigabytes but not had much to say.

(LVM snapshots + kvm = attack this filesystem with multiple tools at once :-)

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

  reply	other threads:[~2014-10-24  2:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 23:16 Check tree block failed, want=17716610236416, have=0 Zygo Blaxell
2014-10-24  0:28 ` Robert White
2014-10-24  1:24   ` Zygo Blaxell
2014-10-24  2:05     ` Zygo Blaxell [this message]
2014-10-24 22:15 ` Check tree block failed, want=17716610236416, have=0 [RESOLVED] Zygo Blaxell

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=20141024020545.GD17380@hungrycats.org \
    --to=ce3g8jdj@umail.furryterror.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rwhite@pobox.com \
    /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.