From: Bruno Kleinert <fuddl@tauware.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: btrfs-progs: improve -D usage description
Date: Fri, 25 Sep 2009 14:16:43 +0200 [thread overview]
Message-ID: <1253881003.27645.12.camel@gummipuppe> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 281 bytes --]
Hi,
when trying out snapshot removal (yeah!) from the for-linus branch I
thought that the help message of btrfsctl could be a bit better. Also
the manpage of btrfsctl lacks information about it.
I attached two micro patches against btrfs-progs-unstable.
Cheers - Fuddl
[-- Attachment #1.2: add-snap-removal-to-man.diff --]
[-- Type: text/x-patch, Size: 807 bytes --]
diff --git a/man/btrfsctl.8.in b/man/btrfsctl.8.in
index c2d4488..36391dc 100644
--- a/man/btrfsctl.8.in
+++ b/man/btrfsctl.8.in
@@ -10,6 +10,7 @@ btrfsctl \- control a btrfs filesystem
[ \fB \-A\fP\fI device\fP ]
[ \fB \-a\fP ]
[ \fB \-c\fP ]
+[ \fB \-D\fP\fI snapshot-name directory\fP ]
.SH DESCRIPTION
.B btrfsctl
is used to control the filesystem and the files and directories stored. It is the tool to create a new snapshot for the filesystem.
@@ -35,6 +36,9 @@ Scans all devices present in the system for btrfs filesystem.
.TP
\fB\-c\fR
Forces a filesystem sync.
+.TP
+\fB\-D\fR \fIsnapshot-name directory\fR
+Deletes a \fIsnapshot\fP in the specified \fIdirectory\fP.
.SH AVAILABILITY
.B btrfsctl
is part of btrfs-progs. Btrfs is currently under heavy development,
[-- Attachment #1.3: improve-snap-removal-help.diff --]
[-- Type: text/x-patch, Size: 1043 bytes --]
diff --git a/btrfsctl.c b/btrfsctl.c
index 66c4e89..e37e2e3 100644
--- a/btrfsctl.c
+++ b/btrfsctl.c
@@ -46,7 +46,7 @@ static inline int ioctl(int fd, int define, void *arg) { return 0; }
static void print_usage(void)
{
printf("usage: btrfsctl [ -d file|dir] [ -s snap_name subvol|tree ]\n");
- printf(" [-r size] [-A device] [-a] [-c] [-D dir .]\n");
+ printf(" [-r size] [-A device] [-a] [-c] [-D snap_name dir]\n");
printf("\t-d filename: defragments one file\n");
printf("\t-d directory: defragments the entire Btree\n");
printf("\t-s snap_name dir: creates a new snapshot of dir\n");
@@ -55,7 +55,7 @@ static void print_usage(void)
printf("\t-A device: scans the device file for a Btrfs filesystem\n");
printf("\t-a: scans all devices for Btrfs filesystems\n");
printf("\t-c: forces a single FS sync\n");
- printf("\t-D: delete snapshot\n");
+ printf("\t-D: snap_name dir: delete named snapshot in directory dir\n");
printf("%s\n", BTRFS_BUILD_VERSION);
exit(1);
}
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2009-09-25 12:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1253881003.27645.12.camel@gummipuppe \
--to=fuddl@tauware.de \
--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