From: Goldwyn Rodrigues <rgoldwyn@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: [btrfs-progs 1/4] Add man/mkfs.btrfs.8.in
Date: Tue, 13 Jan 2009 18:18:02 +0530 [thread overview]
Message-ID: <20090113124802.GA15169@baloo.junglebook> (raw)
Add man/mkfs.btrfs.8.in
Kept the name with the name in, so that further processing such as
BUILD_DATE BUILD_VERSION etc. could be included later.
All man pages included in the man directory to avoid file cluttering.
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.de>
---
man/mkfs.btrfs.8.in | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 63 insertions(+), 0 deletions(-)
create mode 100644 man/mkfs.btrfs.8.in
diff --git a/man/mkfs.btrfs.8.in b/man/mkfs.btrfs.8.in
new file mode 100644
index 0000000..f506665
--- /dev/null
+++ b/man/mkfs.btrfs.8.in
@@ -0,0 +1,63 @@
+.TH MKFS.BTRFS 8
+.SH NAME
+mkfs.btrfs \- create an btrfs filesystem
+.SH SYNOPSIS
+.B mkfs.btrfs
+[ \fB\-A\fP\fI alloc-start\fP ]
+[ \fB\-b\fP\fI byte-count\fP ]
+[ \fB \-d\fP\fI data-profile\fP ]
+[ \fB \-l\fP\fI leafsize\fP ]
+[ \fB \-L\fP\fI label\fP ]
+[ \fB \-m\fP\fI metadata profile\fP ]
+[ \fB \-n\fP\fI nodesize\fP ]
+[ \fB \-s\fP\fI sectorsize\fP ]
+[ \fB \-h\fP ]
+[ \fB \-V\fP ] \fI device\fP [ \fI device ...\fP ]
+.SH DESCRIPTION
+.B mkfs.btrfs
+is used to create an btrfs filesystem (usually in a disk partition, or an array
+of disk partitions).
+.I device
+is the special file corresponding to the device (e.g \fI/dev/sdXX\fP ).
+If multiple \fI devices \fP are specified, btrfs is created
+spanning across the specified \fI devices\fP.
+.SH OPTIONS
+.TP
+\fB\-A\fR, \fB\-\-alloc\-start \fIoffset\fR
+Specify the offset from the start of the device to start the btrfs filesystem. The default value is zero, or the start of the device.
+.TP
+\fB\-b\fR, \fB\-\-byte\-count \fIsize\fR
+Specify the size of the resultant filesystem. If this option is not used,
+mkfs.btrfs uses all the available storage for the filesystem.
+.TP
+\fB\-d\fR, \fB\-\-data \fItype\fR
+Specify how the data must be spanned across the devices specified. Valid
+values are raid0, raid1, raid10 or single.
+.TP
+\fB\-l\fR, \fB\-\-leafsize \fIsize\fR
+Specify the leaf size, the least data item in which btrfs stores data. The
+default value is the page size.
+.TP
+\fB\-L\fR, \fB\-\-label \fIname\fR
+Specify a label for the filesystem.
+.TP
+\fB\-m\fR, \fB\-\-metadata \fIprofile\fR
+Specify how metadata must be spanned across the devices specified. Valid
+values are raid0, raid1, raid10 or single.
+.TP
+\fB\-n\fR, \fB\-\-nodesize \fIsize\fR
+Specify the nodesize. By default the value is set to the pagesize.
+.TP
+\fB\-s\fR, \fB\-\-sectorsize \fIsize\fR
+Specify the sectorsize, the minimum block allocation.
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print the \fBmkfs.btrfs\fP version and exit.
+.SH AVAILABILITY
+.B mkfs.btrfs
+is part of btrfs-progs. Btrfs is currently under heavy development,
+and not suitable for for any uses other than benchmarking and review.
+Please refer to the btrfs wiki
+http://btrfs.wiki.kernel.org for further details.
+.SH SEE ALSO
+.BR btrfsck (8)
--
1.6.0.2
--
Goldwyn
next reply other threads:[~2009-01-13 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 12:48 Goldwyn Rodrigues [this message]
2009-01-15 2:18 ` [btrfs-progs 1/4] Add man/mkfs.btrfs.8.in Chris Mason
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=20090113124802.GA15169@baloo.junglebook \
--to=rgoldwyn@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