linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs unmountable, any btrfs tool segfaults
Date: Sun, 24 Aug 2014 01:21:17 +0000 (UTC)	[thread overview]
Message-ID: <pan$cd143$1f075140$a44693a2$c17a5577@cox.net> (raw)
In-Reply-To: CAGP2HaPx2pXbN=FyBH5MskrsufDXcWtddVfG4Kaie-ZVg=ivJg@mail.gmail.com

Nikolay Shtabel posted on Sat, 23 Aug 2014 16:39:48 +0000 as excerpted:

> After all, the last step is to use btrfs restore:
> 
> btrfs restore -iv /dev/sdc2 /mnt/restore/
> Check tree block failed, want=471748608, have=0
> Check tree block failed, want=471748608, have=0

> read block failed check_tree_block
> Couldn't setup extent tree

> read block failed check_tree_block
> Couldn't setup csum tree

> read block failed check_tree_block
> Segmentation fault [ 3324.252370]

> Can you please suggest any method to restore files from filesystem?

First answer (probably not too helpful, but gets the point across):

Since btrfs is still not fully stable and you are urged to keep backups 
if you value the data, then restore from them.  If you don't have them, 
by definition you obviously don't value the data enough to bother with 
the hassle of backing it up, so no big deal if you lose it, right?

Second answer (hopefully more helpful, but I'm obviously a bit grumpy 
today; I could put off answering until I'm not so grumpy, but I know what 
it's like to be waiting for an answer, so read thru the grumpy and we can 
both hope the solution works):

It used to be common courtesy to read a couple weeks of the the backgroup/
backlist before posting questions as they might be answered already.  I 
guess it isn't so these days...

Anyway, see the second half of the following post (the first half is a 
different problem and solution) dealing with using restore with btrfs-
find-root and etc, along with the wiki link mentioned (and of course the 
manpages as well).  With some luck you can still get btrfs restore 
working.  It worked for me recently (as you can see there, I had backups 
but they weren't as current as I would have liked).

http://permalink.gmane.org/gmane.comp.file-systems.btrfs/37980

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-08-24  1:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-23 16:39 btrfs unmountable, any btrfs tool segfaults Nikolay Shtabel
2014-08-24  1:21 ` Duncan [this message]
2014-08-24  3:07   ` Marc MERLIN
2014-08-24 15:48   ` Nikolay Shtabel

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='pan$cd143$1f075140$a44693a2$c17a5577@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).