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 12:30:01 +1300 [thread overview]
Message-ID: <CADph71zoOB72o2PoUY_qqMsg_TpvBokugR9UzZHo6kPsNm4PNg@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtT5CG4M4nYmmefEfWjapmg3TpMXJSVmTE89r6iPxV6xHw@mail.gmail.com>
> 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 the file system it slows done a ton.
Ok, thanks, looks like there is some other issue then as well. The
process doesn't take up any memory at all, just 100% of one core.
Maybe I'll try to use it with an older version of btrfs-progs, from
Debian Jessie. Don't think it'll make any difference, but I don't know
what else to try. At this point I'm more curious than anything else.
I've got backups for most of my stuff, just a few rogue scripts I'd
have to re-write. Still, would be nice to get those back.
next prev parent reply other threads:[~2016-12-11 23:30 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
2016-12-11 22:46 ` Chris Murphy
2016-12-11 23:30 ` Markus Binsteiner [this message]
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=CADph71zoOB72o2PoUY_qqMsg_TpvBokugR9UzZHo6kPsNm4PNg@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).