From: Maxim Mikheev <mikhmv@gmail.com>
To: Michael <mike@draftx.net>
Cc: Hugo Mills <hugo@carfax.org.uk>,
Liu Bo <liubo2009@cn.fujitsu.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Help with data recovering
Date: Wed, 06 Jun 2012 12:25:41 -0400 [thread overview]
Message-ID: <4FCF8485.4080802@gmail.com> (raw)
In-Reply-To: <CAGJTRciBERUNgRvgx4f4Ns+F2QBwPKUTZ25QCj9LW_=W-4ZoRg@mail.gmail.com>
Option -i was helpful.
Some date was restored.
during restoring some files I got message "ret is -3". This files has 0
size.
Can anyone tell me what is code "-3" mean. Is it recoverable?
So basically data is on harddrives but not completely available.
the questions is: Is it possible to btrfs push to roll back on several
generations?
Thanks
On 06/04/2012 02:37 PM, Michael wrote:
> Below is what you used? So you have RAID 0 for data, RAID 1 for
> metadata. This doesn't help any, but a point of info.
> # Create a filesystem across four drives (metadata mirrored, data striped)
> mkfs.btrfs /dev/sdb /dev/sdc /dev/sdd /dev/sde
>
>
> Just to make sure I understand correctly: This FS with critical info
> used a non-production filesystem, in RAID 0(no redundancy), with no
> backups.
>
> Another option I found(and I am no authority on the subject) is to use
> btrfs.restore with -i
> -i: Ignore errors. Normally the restore tool exits immediately for any
> error. This option forces it to keep going if it can, usually this
> results in some missing data.
> Again, this can be destructive, and it would be very smart to make
> block level copies of everything.
>
> On Mon, Jun 4, 2012 at 1:03 PM, Maxim Mikheev<mikhmv@gmail.com> wrote:
>> It was a RAID0 unfortunately.
>>
>>
>> On 06/04/2012 02:02 PM, Michael wrote:
>>> If he has it in a RAID 1, could he manually fail the bad disk and try
>>> it from there? Obviously this could be harmful, so a dd copy would be
>>> a VERY good idea(truthfully, that should have been the first thing
>>> that was done).
>>> Michael
>>>
>>> On Mon, Jun 4, 2012 at 12:09 PM, Hugo Mills<hugo@carfax.org.uk> wrote:
>>>> On Mon, Jun 04, 2012 at 06:04:22PM +0100, Hugo Mills wrote:
>>>>> I'm out of ideas.
>>>> ... but that's not to say that someone else may have some ideas. I
>>>> wouldn't get your hopes up too much, though.
>>>>
>>>>> 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.
>>>> Hugo.
>>>>
>>>> --
>>>> === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
>>>> PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
>>>> --- A linked list is still a binary tree. Just a very unbalanced ---
>>>> one. -- dragon
next prev parent reply other threads:[~2012-06-06 16:25 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 [this message]
2012-06-07 3:27 ` Maxim Mikheev
2012-06-05 9:55 ` Martin Steigerwald
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=4FCF8485.4080802@gmail.com \
--to=mikhmv@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.com \
--cc=mike@draftx.net \
/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).