From: Piavlo <piavka@cs.bgu.ac.il>
To: Goffredo Baroncelli <kreijack@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC] Move all btrfs command to only one command: btrfs.c
Date: Sun, 24 Jan 2010 20:34:43 +0200 [thread overview]
Message-ID: <4B5C92C3.2090400@cs.bgu.ac.il> (raw)
In-Reply-To: <201001241835.40562.kreijack@libero.it>
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).
>
To avoid such confusion IMHO it's logically better to have two commands
instead one for handling actions at volume level
and other command at file system level - something like btrfs & btrpool
- like in other well known file system :)
Alex
> You can find a git repository in
>
> http://cassiopea.homelinux.net/git/?p=btrfs-command.git;a=summary
>
> select the branch "btrfs-command"
>
> TODO:
> * resizing implementation
> * btrfstune implementation
> * btrfslabel implementation (but it require patch to the kernel)
> * mkfs implementation
> * check of the label length
> * test suite finalisation
> * test, test, test
>
> Suggestions are welcome.
>
> BR
> G.Baroncelli
>
next prev parent reply other threads:[~2010-01-24 18:34 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 [this message]
2010-02-11 16:33 ` Chris Mason
2010-02-11 18:15 ` Goffredo Baroncelli
2010-02-11 21:20 ` rk
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=4B5C92C3.2090400@cs.bgu.ac.il \
--to=piavka@cs.bgu.ac.il \
--cc=kreijack@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).