On Mon, Dec 12, 2016 at 5:12 PM, Chris Murphy wrote:
> Another idea is btrfs-find-root -a. This is slow for me, it took about
> a minute for less than 1GiB of metadata. But I've got over 50
> candidate tree roots and generations.
Same behaviour with the newer versioned
Ok, some news. I chrooted into the old OS-root (Jessie), and low and
behold, old-version btrfs-find-root seemed to work:
# btrfs-find-root /dev/mapper/think--big-home
Super think's the tree root is at 138821632, chunk root 21020672
Well block 4194304 seems great, but generation doesn't match,
> This is what I'd expect if the volume has only had a mkfs done and
> then mounted and umounted. No files. What do you get for
>
> btrfs ins dump-s -fa /dev/mapper/think--big-home
(attached)
Also tried btrfs check -b /dev/mapper/think--big-home, but that errored:
# btrfs check -b
> You might try 'btrfs check' without repairing, using a recent version
> of btrfs-progs and see if it finds anything unusual.
Not quite sure what that output means, but btrfs check returns instantly:
$ sudo btrfs check /dev/mapper/think--big-home
Checking filesystem on
> OK when I do it on a file system with just 14GiB of metadata it's
> maybe 15 seconds. So a few minutes sounds sorta suspicious to me but,
> *shrug* I don't have a file system the same size to try it on, maybe
> it's a memory intensive task and once the system gets low on RAM while
> traversing
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 <li...@colorremedies.com> wrote:
> On Sat, Dec 10, 2016 at 5:12 PM, Markus Binsteiner <mak...@gmai
s been enabled before deletion,
> or the volume has been mannually generated snapshots, then probably it might
> be able to perform fast recover.
>
> Regards,
> Xin
>
> Sent: Saturday, December 10, 2016 at 4:12 PM
> From: "Markus Binsteiner" <mak...@gmail.com>
> To: li
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