Re: btrfs-find-root duration?

ber 10, 2016 at 4:12 PM From: "Markus Binsteiner" <mak...@gmail.com> To: linux-btrfs@vger.kernel.org Subject: btrfs-find-root duration? 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 r

Re: btrfs-find-root duration?

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

Re: btrfs-find-root duration?

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,

Re: btrfs-find-root duration?

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. But still you can try the tree root for the oldest generation in your full superblock listing, like I described. If that

Re: btrfs-find-root duration?

I don't know, maybe. This is not a new file system, clearly, it has half million+ generations. backup_roots[4]: backup 0: backup_tree_root:29360128gen: 593817level: 1 backup_chunk_root:20971520gen: 591139level: 1 backup_extent_root:29376512

Re: btrfs-find-root duration?

> 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

Re: btrfs-find-root duration?

On Sun, Dec 11, 2016 at 5:12 PM, Markus Binsteiner wrote: >> 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

Re: btrfs-find-root duration?

> 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

Re: btrfs-find-root duration?

On Sun, Dec 11, 2016 at 4:30 PM, Markus Binsteiner wrote: >> 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

Re: btrfs-find-root duration?

> 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

Re: btrfs-find-root duration?

Yes. Command and device only. > > I've tried that initially, but it run for a few hours with no output > beside the initial 'Superblock...'. 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

Re: btrfs-find-root duration?

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

Re: btrfs-find-root duration?

On Sat, Dec 10, 2016 at 5:12 PM, Markus Binsteiner 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

Re: btrfs-find-root duration?

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

Re: btrfs-find-root duration?

, 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: linux-btrfs@vger.kernel.org Subject: btrfs-find-root duration? It seems I've accidentally deleted all files in m

btrfs-find-root duration?

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