From: divya.indi@oracle.com
To: dsterba@suse.cz, Graham Cobb <g.btrfs@cobb.uk.net>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 3/3] btrfs-progs: Add command to check if balance op is req
Date: Tue, 1 Nov 2016 17:39:39 -0700 [thread overview]
Message-ID: <d4965a6b-b3a8-7d12-aa63-5e7c6fc66a57@oracle.com> (raw)
In-Reply-To: <20161031163342.GP12522@twin.jikos.cz>
On 10/31/2016 09:33 AM, David Sterba wrote:
> On Fri, Oct 28, 2016 at 05:29:45PM +0100, Graham Cobb wrote:
>> On 28/10/16 16:20, David Sterba wrote:
>>> I tend to agree with this approach. The usecase, with some random sample
>>> balance options:
>>>
>>> $ btrfs balance start --analyze -dusage=10 -musage=5 /path
>> Wouldn't a "balance analyze" command be better than "balance start
>> --analyze"? I would have guessed the latter started the balance but
>> printed some analysis as well (before or, probably more usefully,
>> afterwards).
> Right, separate command seems better.
What about btrfs inspect-internal bg_analysis (new name:
show-block-groups)? It can still be a subcommand for inspect-internal?
So, wel have 2 new sub commands:
1) btrfs balance analyze
2) btrfs inspect-internal show-block-groups
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-11-02 0:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 0:35 btrfs-progs: Add 2 new subcommands to inspect-internal Divya Indi
2016-10-18 0:35 ` [PATCH 1/3] btrfs-progs: Generic functions to retrieve chunks and their bg info Divya Indi
2016-10-18 0:35 ` [PATCH 2/3] btrfs-progs: Add a command to show " Divya Indi
2016-10-18 0:35 ` [PATCH 3/3] btrfs-progs: Add command to check if balance op is req Divya Indi
2016-10-18 1:42 ` Qu Wenruo
2016-10-19 17:08 ` Divya Indi
2016-10-28 15:20 ` David Sterba
2016-10-28 16:29 ` Graham Cobb
2016-10-31 16:33 ` David Sterba
2016-11-02 0:39 ` divya.indi [this message]
2016-10-30 14:10 ` Qu Wenruo
2016-10-18 1:39 ` [PATCH 2/3] btrfs-progs: Add a command to show bg info Qu Wenruo
2016-10-18 5:24 ` Roman Mamedov
2016-10-19 17:33 ` Divya Indi
2016-10-28 16:00 ` David Sterba
2016-11-02 0:40 ` divya.indi
2016-10-18 1:34 ` [PATCH 1/3] btrfs-progs: Generic functions to retrieve chunks and their " Qu Wenruo
2016-10-28 15:44 ` David Sterba
2016-11-02 0:39 ` divya.indi
2017-06-07 17:03 ` Goffredo Baroncelli
2017-06-09 21:57 ` divya.indi
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=d4965a6b-b3a8-7d12-aa63-5e7c6fc66a57@oracle.com \
--to=divya.indi@oracle.com \
--cc=dsterba@suse.cz \
--cc=g.btrfs@cobb.uk.net \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.