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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
