From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS error: bad tree block start 0 623771648
Date: Wed, 2 Aug 2017 03:22:32 +0000 (UTC) [thread overview]
Message-ID: <pan$4d60$25808f7d$ec32dcbb$a11fc6f7@cox.net> (raw)
In-Reply-To: 20170801110805.09226fc3@natsu
Roman Mamedov posted on Tue, 01 Aug 2017 11:08:05 +0500 as excerpted:
> On Sun, 30 Jul 2017 18:14:35 +0200 "marcel.cochem"
> <marcel.cochem@googlemail.com> wrote:
>
>> I am pretty sure that not all data is lost as i can grep thorugh the
>> 100 GB SSD partition. But my question is, if there is a tool to rescue
>> all (intact) data and maybe have only a few corrupt files which can't
>> be recovered.
>
> There is such a tool, see
> https://btrfs.wiki.kernel.org/index.php/Restore
I was going to suggest that too... and even started a reply to do so...
upon which I read a bit closer and saw he'd actually tried restore
already...
And before you suggest it, he tried btrfs-find-root as well, and it
didn't work either, so he can't do the advanced/technical mode of
restore, feeding it addresses from btrfs-find-root, either. =:^(
It's in the post...
So unfortunately he's pretty much left with manual hacking and scraping,
and that's at a level beyond what I at least am able to help him with...
--
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
prev parent reply other threads:[~2017-08-02 3:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 16:14 BTRFS error: bad tree block start 0 623771648 marcel.cochem
2017-07-31 18:12 ` Liu Bo
2017-08-01 6:04 ` Roman Mamedov
2017-08-01 21:45 ` Liu Bo
2017-08-02 8:30 ` marcel.cochem
2017-08-01 6:08 ` Roman Mamedov
2017-08-02 3:22 ` Duncan [this message]
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$4d60$25808f7d$ec32dcbb$a11fc6f7@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 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.