From: "Michael Niederle" <mniederle@gmx.at>
To: Goffredo Baroncelli <kreijack@gmail.com>
Cc: linux-btrfs@vger.kernel.org, David Nicol <davidnicol@gmail.com>,
taruishi.hiroak@jp.fujitsu.com
Subject: Re: [RFC] Move all btrfs command to only one command
Date: Fri, 22 Jan 2010 01:11:07 +0100 [thread overview]
Message-ID: <20100122011107.7bc36b2b@simplux> (raw)
In-Reply-To: <201001212029.26681.kreijack@libero.it>
> $ btrfs
> Usage:
> btrfs clone|-c <source> [<dest>/]<name>
> Clone the subvolume <source> with the name <name> in the
> <dest>
> directory.
> btrfs delete|-d
> <subvolume> Delete the subvolume <subvolume>.
> btrfs create|-C [<dest>/]<name>
> Create a subvolume in <dest> (or the current directory if not
> passed.
> btrfs defrag|-d <file>|<dir> [<file>|<dir>...]
> Defragment a file or a directory.
> btrfs fssync|-s <path>
> Force a fs sync on the filesystem <path>
> btrfs resize|-r [+/-]<newsize>[gkm]|max <filesystem>
> Resize the file system. If 'max' is passed, the filesystem
> will occupe all available space on the device.
> btrfs scan|-S [<device> [<device>..]
> Scan all device for or the passed device for a btrfs
> filesystem.
> btrfs show|-l <dev>|<label> [<dev>|<label>.. ]
> Show the btrfs devices
> btrfs balance|-b <path>
> Balance teh chunk across the device
> btrfs add|-A <dev> <path>
> Add a device to a filesystem
> btrfs rem|-R <dev> <path>
> Remove a device to a filesystem
>
> btrfs help|--help|-h
> Show the help.
I like this idea!
Just a small suggestion:
"btrfs remove" instead of "btrfs rem"
-----
Another question: Is there a simple way to convert a directory into a subvolume?
Currently I first create the new subvolume; copy or move the data of the
directory into the new subvolume, then delete the directory and finally
rename the subvolume.
Greetings, Michael
next prev parent reply other threads:[~2010-01-22 0:11 UTC|newest]
Thread overview: 26+ 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 [this message]
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
2010-02-11 21:29 ` Goffredo Baroncelli
-- strict thread matches above, loose matches on Subject: below --
2010-08-19 20:52 [RFC] Move all btrfs command to only one command James Smith
2010-08-20 12:03 ` Goffredo Baroncelli
2010-08-20 12:43 ` Jon Nelson
2010-08-20 14:42 ` Benjamin Griese
2010-08-20 18:56 ` Goffredo Baroncelli
2010-08-20 18:27 ` Josh Berry
2010-08-20 18:34 ` Andreas Philipp
2010-08-20 18:49 ` Josh Berry
2010-08-20 19:00 ` Andreas Philipp
2010-08-20 20:28 ` Josh Berry
2010-08-21 4:51 ` James Smith
2010-08-21 9:37 ` Goffredo Baroncelli
[not found] ` <AANLkTikJd8bDU1Eq22u0+yQ8eBCUn3OXHoE5E7uy+SG=@mail.gmail.com>
[not found] ` <AANLkTi=VpZv26jntJ8mwmxtjnQ5LDOn_MSm6VtEhJ1CB@mail.gmail.com>
2010-08-27 3:38 ` James Smith
2010-08-20 19:03 ` Goffredo Baroncelli
2010-08-20 12:12 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=20100122011107.7bc36b2b@simplux \
--to=mniederle@gmx.at \
--cc=davidnicol@gmail.com \
--cc=kreijack@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=taruishi.hiroak@jp.fujitsu.com \
/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).