From: rk <rkasl@computer.org>
To: linux-btrfs@vger.kernel.org, Michael Niederle <mniederle@gmx.at>,
Xavier Nicollet <nicollet@jeru.org>,
Adrian von Bidder <avbidder@fortytwo.ch>
Subject: Re: [RFC] Move all btrfs command to only one command: btrfs.c
Date: Thu, 11 Feb 2010 16:20:07 -0500 [thread overview]
Message-ID: <4B747487.8000401@computer.org> (raw)
In-Reply-To: <20100211163342.GA11297@think>
.. it would be good to have some "mechanism" that will "prevent" people
mixing -d with -D
Chris Mason wrote:
> On Sun, Jan 24, 2010 at 06:35:33PM +0100, Goffredo Baroncelli wrote:
>
>> Hi all,
>>
>> this is a follow-up of the previous email. I rewrite the btrfs command in C.
>> Now the following actions are implemented:
>>
>> snapshot (-s) -> create a snapshot
>> delete (-D) -> delete a subvolume or a snapshot
>> create (-S) -> create a subvolume
>> defrag (-d) -> defrag a tree or a file
>> fssync (-c) -> sync a filesystem
>> scan (-a) -> scan devices searching a btrfs filesystem
>> show (-l) -> list the btrfs fs and its volumes
>> balance (-b) -> balance the chunk across the volumes
>> add-dev (-A) -> add a volume to a filesystem
>> rem-dev (-R) -> remove a volume to a filesystem
>>
>> I cared that btrfs returns appropriate error code. And I check that a correct
>> parameters number is passed. Finally, where appropriate if a subvolume is
>> required (for example in case of snapshot and or delete) is checked that the
>> passed path is a subvolume. This should limits the complain like:
>> - I snapshot a sub directory, but I got a snapshot of the entire tree.
>>
>> I renamed remove (a volume) in rem-dev in order to avoid confusion with delete
>> (a subvolume).
>>
>
> Sorry for the late reply, but I really like this mode and will work on
> integrating it. rem-dev should be rm-dev or remove-dev
>
> -chris
> --
> 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:[~2010-02-11 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 19:29 [RFC] Move all btrfs command to only one command Goffredo Baroncelli
2010-01-22 0:02 ` TARUISI Hiroaki
2010-01-22 0:11 ` Michael Niederle
2010-01-22 9:33 ` Xavier Nicollet
2010-01-22 8:23 ` Adrian von Bidder
2010-01-24 17:35 ` [RFC] Move all btrfs command to only one command: btrfs.c Goffredo Baroncelli
2010-01-24 18:34 ` Piavlo
2010-02-11 16:33 ` Chris Mason
2010-02-11 18:15 ` Goffredo Baroncelli
2010-02-11 21:20 ` rk [this message]
2010-02-11 21:29 ` Goffredo Baroncelli
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=4B747487.8000401@computer.org \
--to=rkasl@computer.org \
--cc=avbidder@fortytwo.ch \
--cc=linux-btrfs@vger.kernel.org \
--cc=mniederle@gmx.at \
--cc=nicollet@jeru.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).