From: Markus Binsteiner <makkus@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-find-root duration?
Date: Mon, 12 Dec 2016 11:41:45 +1300 [thread overview]
Message-ID: <CADph71wae2AQT-v-hu0YcJdNE+dWxRZ7yQVmMEMLyhzsC-FHqQ@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtTC5T0v6jZpALTPwn=CvWn-kJXZX2vVFAEjjk9xokqoPQ@mail.gmail.com>
I recon it took me about 5 minutes to realise what I'd done, then I
unmounted the volume. I don't think I wrote anything inbetween, but
there were a few applications open at that time, so there might have
been some i/o.
When you say 'by itself', you mean without the '-o 5'?
I've tried that initially, but it run for a few hours with no output
beside the initial 'Superblock...'. I realized I forgot to redirect
the stdout which I thought that would be a good idea so I restarted it
with '-o 5' (found some advice said that's the thing to do if it was
the root subvolume that was deleted).
Anyway, restarted it without '-o 5', let's see whether it makes any
difference. Is there any indication on how long it should take? Just
roughly, hours, days? I've got about 150GB of data on that partition I
think. Also, is there supposed to be incremental output, or will it be
one big wall of text once it's finished?
As I said, when I tried before there was no output at all for hours,
which seemed a bit strange.
Thanks for your help!
On Sun, Dec 11, 2016 at 6:47 PM, Chris Murphy <lists@colorremedies.com> wrote:
> On Sat, Dec 10, 2016 at 5:12 PM, Markus Binsteiner <makkus@gmail.com> wrote:
>> It seems I've accidentally deleted all files in my home directory,
>> which sits in its own btrfs partition (lvm on luks). Now I'm trying to
>> find the roots to be able to use btrfs restore later on.
>>
>> btrfs-find-root seems to be taking ages though. I've run it like so:
>>
>> btrfs-find-root /dev/mapper/think--big-home -o 5 > roots.txt
>
> Uhh, just do btrfs-find-root by itself to get everything it can find.
> And then work backwards from the most recent generation using btrfs
> restore -t using each root bytenr from btrfs-find-root. The more
> recent the generation, the better your luck that it hasn't been
> overwritten yet; but too recent and your data may not exist in that
> root. It really depends how fast you umounted the volume after
> deleting everything.
>
>
>
> --
> Chris Murphy
next prev parent reply other threads:[~2016-12-11 22:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 0:12 btrfs-find-root duration? Markus Binsteiner
2016-12-11 1:20 ` Xin Zhou
[not found] ` <trinity-19716973-6bfa-438e-8068-ccb3d257eaad-1481419066346@3capp-mailcom-bs02>
2016-12-11 1:42 ` Markus Binsteiner
2016-12-12 12:14 ` Austin S. Hemmelgarn
2016-12-11 5:47 ` Chris Murphy
2016-12-11 22:41 ` Markus Binsteiner [this message]
2016-12-11 22:46 ` Chris Murphy
2016-12-11 23:30 ` Markus Binsteiner
2016-12-11 23:41 ` Chris Murphy
2016-12-12 0:12 ` Markus Binsteiner
2016-12-12 1:12 ` Chris Murphy
2016-12-12 2:10 ` Markus Binsteiner
2016-12-12 4:06 ` Chris Murphy
2016-12-12 4:12 ` Chris Murphy
2016-12-12 4:31 ` Markus Binsteiner
2016-12-12 4:19 ` Markus Binsteiner
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=CADph71wae2AQT-v-hu0YcJdNE+dWxRZ7yQVmMEMLyhzsC-FHqQ@mail.gmail.com \
--to=makkus@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).