From: Goffredo Baroncelli <kreijack@inwind.it>
To: Ilya Dryomov <idryomov@gmail.com>, Hugo Mills <hugo@carfax.org.uk>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH 0/3] Btrfs-progs: restriper interface
Date: Sat, 4 Feb 2012 14:06:28 +0100 [thread overview]
Message-ID: <201202041406.28273.kreijack@inwind.it> (raw)
In-Reply-To: <1328305752-32160-1-git-send-email-idryomov@gmail.com>
Hi Ilya,
On Friday, 03 February, 2012 22:49:09 Ilya Dryomov wrote:
> Hello,
>
> This is the userspace part of restriper, rebased onto the new progs
> infrastructure. Restriper commands are located under 'balance' prefix,
> which is now the top level command group. However to not confuse
> existing users 'balance' prefix is also available under 'filesystem':
>
> btrfs [filesystem] balance start
> btrfs [filesystem] balance pause
> btrfs [filesystem] balance cancel
> btrfs [filesystem] balance resume
> btrfs [filesystem] balance status
>
> Backwards compatibility is fully preserved thanks to the new command
> parser: the old 'btrfs filesystem balance <path>' works as expected.
I prefer to avoid prefix which may confuse the user. If I have a subvolume
called "s", what means:
btrfs filesystem balance s
Is it a missing argument (the path required for btrfs filesystem balance) or
is it a synonymus of
btrfs filesystem balance start ./s
(or btrfs filesystem balance stop ./s)
?
To me I prefer to add another family of command called
btrfs balance *
and to leave
btrfs filesystem balance
as synonymus of
btrfs balance start
This was discussed several years ago. Allowing the user to abbreviate the
commands fights with the ability to have different length of commands , when
an option could beconfused with a command (s vs start/stop....).
>
> The patchset is on top of the new parser posted half an hour ago,
> available at:
>
> git://github.com/idryomov/btrfs-progs.git restriper
>
> Thanks,
>
> Ilya
>
>
> Ilya Dryomov (3):
> Btrfs-progs: add restriper headers
> Btrfs-progs: add 'balance' command group infrastructure
> Btrfs-progs: add restriper commands
>
> Makefile | 2 +-
> btrfs.c | 1 +
> cmds-balance.c | 684
> +++++++++++++++++++++++++++++++++++++++++++++++++++++ cmds-filesystem.c |
> 38 +---
> commands.h | 2 +
> ctree.h | 23 ++-
> ioctl.h | 53 ++++
> print-tree.c | 6 +
> volumes.h | 31 +++
> 9 files changed, 795 insertions(+), 45 deletions(-)
> create mode 100644 cmds-balance.c
next prev parent reply other threads:[~2012-02-04 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 21:49 [PATCH 0/3] Btrfs-progs: restriper interface Ilya Dryomov
2012-02-03 21:49 ` [PATCH 1/3] Btrfs-progs: add restriper headers Ilya Dryomov
2012-02-03 21:49 ` [PATCH 2/3] Btrfs-progs: add 'balance' command group infrastructure Ilya Dryomov
2012-02-03 21:49 ` [PATCH 3/3] Btrfs-progs: add restriper commands Ilya Dryomov
2012-02-03 22:13 ` [PATCH 0/3] Btrfs-progs: restriper interface Hugo Mills
2012-02-05 15:40 ` Chris Mason
2012-02-04 13:06 ` Goffredo Baroncelli [this message]
2012-02-04 14:47 ` Ilya Dryomov
2012-02-06 22:20 ` Goffredo Baroncelli
2012-02-07 9:30 ` Ilya Dryomov
2012-02-07 11:05 ` Hugo Mills
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=201202041406.28273.kreijack@inwind.it \
--to=kreijack@inwind.it \
--cc=chris.mason@oracle.com \
--cc=hugo@carfax.org.uk \
--cc=idryomov@gmail.com \
--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 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).