From: Goffredo Baroncelli <kreijack@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>,
kreijack@inwind.it, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 5/5] Add man page description for nCmSpP replication levels
Date: Sun, 10 Mar 2013 18:52:59 +0100 [thread overview]
Message-ID: <513CC87B.50005@gmail.com> (raw)
In-Reply-To: <20130310172009.GC30771@carfax.org.uk>
On 03/10/2013 06:20 PM, Hugo Mills wrote:
> On Sun, Mar 10, 2013 at 03:01:12PM +0100, Goffredo Baroncelli wrote:
>> Hi Hugo,
>>
>> could you please add also to the btrfs man page a section where are
>> described the nCmSpP levels ?
>>
>> Thanks.
>> GB
>>
>>
>>
>> On 03/09/2013 09:31 PM, Hugo Mills wrote:
>>> Signed-off-by: Hugo Mills <hugo@carfax.org.uk>
>>> ---
> [snip]
>>> diff --git a/man/mkfs.btrfs.8.in b/man/mkfs.btrfs.8.in
>>> index 41163e0..2e71e65 100644
>>> --- a/man/mkfs.btrfs.8.in
>>> +++ b/man/mkfs.btrfs.8.in
>>> @@ -37,7 +37,29 @@ 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.
>
> Like here?
Yes, I thought about a section which lists the allowable raid level.
>
>>> +values are of the form <n>C[D][<m>S[<p>P]], where <n> is the number of copies
>>> +of data, <m> is the number of stripes per copy, and <p> is the number of parity
>>> +stripes. The <m> parameter must (currently) be a literal "m", indicating that
>>> +as many stripes as possible will be used. The letter D may be added to the
>>> +number of copies, to indicate non-redundant copies (e.g. on the same device).
>>> +
>>> +The following deprecated values may also be used:
>>> +.RS 16
>>> +.P
>>> +single 1C
>>> +.P
>>> +raid0 1CmS
>>> +.P
>>> +raid1 2C
>>> +.P
>>> +dup 2CD
>>> +.P
>>> +raid10 2CmS
>>> +.P
>>> +raid5 1CmS1P
>>> +.P
>>> +raid6 1CmS2P
>>> +.RS -16
>>> .TP
>>> \fB\-f\fR
>>> Force overwrite when an existing filesystem is detected on the device.
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2013-03-10 17:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 20:31 [PATCH 0/5] [RFC] RAID-level terminology change Hugo Mills
2013-03-09 20:31 ` [PATCH 1/5] Use nCmSpP format for mkfs Hugo Mills
2013-03-09 20:31 ` [PATCH 2/5] Move parse_profile to utils.c Hugo Mills
2013-03-09 20:31 ` [PATCH 3/5] Convert balance filter parser to use common nCmSpP replication-level parser Hugo Mills
2013-03-09 20:31 ` [PATCH 4/5] Change output of btrfs fi df to report new (or old) RAID names Hugo Mills
2013-03-09 20:31 ` [PATCH 5/5] Add man page description for nCmSpP replication levels Hugo Mills
2013-03-10 14:01 ` Goffredo Baroncelli
2013-03-10 17:20 ` Hugo Mills
2013-03-10 17:52 ` Goffredo Baroncelli [this message]
2013-03-09 21:38 ` [PATCH 0/5] [RFC] RAID-level terminology change Harald Glatt
[not found] ` <CAFWF=am4ki529Zez4123gYk3BD+Z9RONRpAK7NZe=skHzcdMiw@mail.gmail.com>
2013-03-09 21:46 ` Hugo Mills
2013-03-09 22:25 ` Roger Binns
2013-03-10 1:44 ` Hugo Mills
2013-03-10 5:41 ` Roger Binns
2013-03-10 6:29 ` Harald Glatt
2013-03-10 6:37 ` Harald Glatt
2013-03-10 11:31 ` Martin Steigerwald
2013-03-10 11:48 ` Roger Binns
2013-03-10 22:04 ` Hugo Mills
2013-03-11 0:21 ` Roger Binns
2013-03-27 4:27 ` Brendan Hide
2013-03-27 5:24 ` Roger Binns
2013-03-10 11:23 ` Martin Steigerwald
2013-03-10 14:11 ` Goffredo Baroncelli
2013-03-10 21:36 ` Hugo Mills
2013-03-10 21:45 ` Harald Glatt
2013-03-10 22:59 ` Goffredo Baroncelli
2013-03-10 22:06 ` Harald Glatt
2013-03-10 23:06 ` Diego Calleja
2013-03-10 15:43 ` Goffredo Baroncelli
2013-03-10 22:24 ` Hugo Mills
2013-03-10 22:42 ` Harald Glatt
2013-03-10 23:40 ` sam tygier
2013-03-10 23:49 ` Hugo Mills
2013-03-11 14:14 ` David Sterba
2013-03-10 23:55 ` sam tygier
2013-03-11 8:56 ` Hugo Mills
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=513CC87B.50005@gmail.com \
--to=kreijack@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=kreijack@inwind.it \
--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