From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Hugo Mills <hugo@carfax.org.uk>, Maxim Mikheev <mikhmv@gmail.com>,
Liu Bo <liubo2009@cn.fujitsu.com>
Subject: Re: Help with data recovering
Date: Tue, 5 Jun 2012 11:55:14 +0200 [thread overview]
Message-ID: <201206051155.14398.Martin@lichtvoll.de> (raw)
In-Reply-To: <20120604170422.GD15986@carfax.org.uk>
Am Montag, 4. Juni 2012 schrieb Hugo Mills:
> On Mon, Jun 04, 2012 at 12:24:05PM -0400, Maxim Mikheev wrote:
> > I run through all potential tree roots. It gave me everytime
> > messages like these:
> >
> > parent transid verify failed on 3405159735296 wanted 9096 found 5263
> > parent transid verify failed on 3405159735296 wanted 9096 found 5263
[…]
> > The largest recovered data is 12Kb.
> > max@s0:~/btrfs-recovering./recovered$ ls -lahs 3728819929088
> > total 28K
> > 4.0K drwxr-xr-x 3 root root 4.0K Jun 4 12:06 .
[…]
> > What can I do next?
>
> I'm out of ideas.
>
> At this point, though, you're probably looking at somebody writing
> custom code to scan the FS and attempt to find and retrieve anything
> that's recoverable.
>
> You might try writing a tool to scan all the disks for useful
> fragments of old trees, and see if you can find some of the tree roots
> independently of the tree of tree roots (which clearly isn't
> particularly functional right now). You might try simply scanning the
> disks looking for your lost data, and try to reconstruct as much of it
> as you can from that. You could try to find a company specialising in
> data recovery and pay them to try to get your data back. Or you might
> just have to accept that the data's gone and work on reconstructing
> it.
Only thing that comes to my mind thats still tryable without involving a
data recover firm or engage a developer for an improved recovery tool is:
PhotoRec from testdisk package or some other data recovery tool that looks
for headers for known fileformats like I think foremost.
It has some drawbacks:
- AFAIK it has no means to glue back together fragmented files, so these
are likely gone or truncated
- filenames are lost
- directory structure is lost
I think it has been said, but I think its important to repeat it:
BTRFS - or any other filesystem - with RAID 0 without backup is not for
important production data. Not ever. Maxim, I suggest if you learn
anything out of this let it be at least this.
When I think about your setup, Maxim, the sentence "I want to have my data
destroyed" comes to my mind.
I would try with photorec from testdisk first. Its quite easy to use.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2012-06-05 9:55 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 22:14 Help with recover data Maxim Mikheev
2012-05-29 22:40 ` Help with data recovering Maxim Mikheev
2012-05-29 23:11 ` cwillu
2012-05-29 23:24 ` Maxim Mikheev
2012-05-29 23:36 ` cwillu
2012-05-31 2:02 ` Maxim Mikheev
[not found] ` <CA+WRLO-mRoSXkdd6_ydc2py3JJCnoM4avQNanxDWWntde2Ah0A@mail.gmail.com>
2012-06-01 21:15 ` Maxim Mikheev
[not found] ` <CAGJTRcibT_pufU4tKqbBpBfm8QiuW=dhQ8BAGzQnpxMCa-dOCQ@mail.gmail.com>
2012-06-02 13:43 ` Maxim Mikheev
2012-06-04 1:22 ` Liu Bo
2012-06-04 1:43 ` Maxim Mikheev
2012-06-04 2:16 ` Liu Bo
2012-06-04 2:18 ` Maxim Mikheev
2012-06-04 2:59 ` Liu Bo
2012-06-04 3:13 ` Maxim Mikheev
2012-06-04 4:27 ` Maxim Mikheev
2012-06-04 8:18 ` Arne Jansen
2012-06-04 11:30 ` Maxim Mikheev
2012-06-04 11:32 ` Arne Jansen
2012-06-04 11:43 ` Maxim Mikheev
2012-06-04 11:49 ` Hugo Mills
2012-06-04 12:01 ` Maxim Mikheev
2012-06-04 12:11 ` Hugo Mills
2012-06-04 12:28 ` Maxim Mikheev
2012-06-04 12:34 ` Hugo Mills
2012-06-04 12:37 ` Maxim Mikheev
2012-06-04 16:24 ` Maxim Mikheev
2012-06-04 17:04 ` Hugo Mills
2012-06-04 17:09 ` Hugo Mills
2012-06-04 18:02 ` Michael
2012-06-04 18:03 ` Maxim Mikheev
2012-06-04 18:37 ` Michael
2012-06-06 16:25 ` Maxim Mikheev
2012-06-07 3:27 ` Maxim Mikheev
2012-06-05 9:55 ` Martin Steigerwald [this message]
2012-06-05 9:57 ` Martin Steigerwald
2012-06-04 14:54 ` Ryan C. Underwood
2012-06-04 16:49 ` Maxim Mikheev
2012-06-05 9:59 ` Martin Steigerwald
2012-06-05 10:23 ` Martin Steigerwald
2012-06-05 11:07 ` Helmut Hullen
2012-05-29 23:37 ` Maxim Mikheev
2012-05-29 23:14 ` Help with recover data Felix Blanke
2012-05-29 23:19 ` cwillu
2012-06-04 12:24 ` Stefan Behrens
2012-06-04 12:26 ` Maxim Mikheev
2012-06-04 13:03 ` Stefan Behrens
[not found] ` <4FCCC176.1020007@gmail.com>
2012-06-04 15:01 ` Maxim Mikheev
2012-06-04 15:02 ` Stefan Behrens
2012-06-04 15:08 ` Maxim Mikheev
2012-06-04 15:11 ` Stefan Behrens
2012-06-04 15:26 ` Maxim Mikheev
2012-06-04 17:35 ` Maxim Mikheev
2012-06-04 18:08 ` Stefan Behrens
2012-06-04 18:15 ` Ryan C. Underwood
2012-06-04 12:31 ` Maxim Mikheev
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=201206051155.14398.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.com \
--cc=mikhmv@gmail.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 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).