linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 17:31:28 +1300	[thread overview]
Message-ID: <CADph71ww05nUn5NFpo92FXPJt0p0ft8sc_-AN-OTuYPC13BGhg@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtQ0niBwPjVyR8G2Lkyu3-yCzkAiD8cN1WHEVezG0xrP3Q@mail.gmail.com>

On Mon, Dec 12, 2016 at 5:12 PM, Chris Murphy <lists@colorremedies.com> 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 btrfs-find-root, just hangs.
The older one doesn't seem to have that option.

  reply	other threads:[~2016-12-12  4:31 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
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 [this message]
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=CADph71ww05nUn5NFpo92FXPJt0p0ft8sc_-AN-OTuYPC13BGhg@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).