From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Actual effect of mkfs.btrfs -m raid10 </dev/sdX> ... -d raid10 </dev/sdX> ...
Date: Tue, 19 Nov 2013 21:04:49 +0000 (UTC) [thread overview]
Message-ID: <pan$bf2c2$464ddc53$a304706e$f524e2ac@cox.net> (raw)
In-Reply-To: CAEWPe=rMXVehpFNko-wZ1i4dKP21J8wJKj1R2jDSK2HsEYmduQ@mail.gmail.com
deadhorseconsulting posted on Tue, 19 Nov 2013 13:24:01 -0600 as
excerpted:
> Interesting, this confirms what I was observing.
> Given the wording in man pages for "-m" and "-d" which states "Specify
> how the metadata or data must be spanned across the devices specified."
> I took "devices specified" to literally mean the devices specified after
> the according switch.
It's all in how you read the documentation. After years of doing so...
While I can see how you might get that from reading the -m and -d option
text descriptions, the synopsis indicates differently (excerpt quotes
reformatted for posting):
SYNOPSIS
mkfs.btrfs [ -A alloc-start ] [ -b byte-count ] [ -d data-profile ]
[ -f ] [ -n node‐size ] [ -l leafsize ] [ -L label ] [ -m metadata
profile ] [ -M mixed data+metadata ] [ -s sectorsize ] [ -r rootdir ]
[ -K ] [ -O feature1,feature2,... ] [ -h ] [ -V ] device [ device ... ]
Here, you can see that the -d and -m options take only a single
parameter, the profile, and that the device list goes at the end and is
thus a general device list, not specifically linked to the -d and -m
options.
Similarly, the option lines themselves:
-d, --data type
-m, --metadata profile
... not...
-d, --data type [ device [ device ... ]]
-m, --metdata profile [ device [ device ...]]
Those are from the manpage. Similarly, the usage line from the output of
mkfs.btrfs --help (--help being an unrecognized option it says, but it
does what it needs to do...):
usage: mkfs.btrfs [options] dev [ dev ... ]
options:
-d --data data profile, raid0, raid1, raid5, raid6, raid10, dup or single
-m --metadata metadata profile, values like data profile
All options come first, no indication of per-option device list, then the
general purpose devices list.
So I'd argue that the documentation's reasonably clear as-is, no per-
option device list, general purpose device list at the end, thus no
ability to specify data-specific and metadata-specific device lists.
(Of course it can happen that the code gets out of sync with the
documentation, but that wasn't the argument here.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-11-19 21:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 5:12 Actual effect of mkfs.btrfs -m raid10 </dev/sdX> ... -d raid10 </dev/sdX> deadhorseconsulting
2013-11-19 9:06 ` Hugo Mills
2013-11-19 19:24 ` deadhorseconsulting
2013-11-19 21:04 ` Duncan [this message]
2013-11-20 6:41 ` Martin
2013-11-19 23:16 ` Duncan
2013-11-20 6:35 ` Martin
2013-11-20 10:16 ` Chris Murphy
2013-11-20 10:22 ` Russell Coker
2013-11-20 8:09 ` Hugo Mills
2013-11-20 16:43 ` Duncan
2013-11-20 16:52 ` Hugo Mills
2013-11-20 21:13 ` Duncan
2013-11-21 17:14 ` Jeff Mahoney
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='pan$bf2c2$464ddc53$a304706e$f524e2ac@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).