From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: copies= option
Date: Mon, 5 May 2014 02:59:35 +0000 (UTC) [thread overview]
Message-ID: <pan$dabcf$295111b1$f1cac574$f1f862c3@cox.net> (raw)
In-Reply-To: 20140504183155.GK24298@carfax.org.uk
Hugo Mills posted on Sun, 04 May 2014 19:31:55 +0100 as excerpted:
> My proposal was simply a description mechanism, not an
> implementation. The description is N-copies, M-device-stripe,
> P-parity-devices (NcMsPp), and (more or less comfortably) covers at
> minimum all of the current and currently-proposed replication levels.
> There's a couple of tweaks covering description of allocation rules
> (DUP vs RAID-1).
Thanks. That was it. =:^)
But I had interpreted the discussion as a bit more concrete in terms of
ultimate implementation than it apparently was. Anyway, it would indeed
be nice to see an eventual implementation such that the above notation
could be used with, for instance, mkfs.btrfs, and
btrfs balance start -Xconvert, but regardless, that does look to be a way
off.
--
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:[~2014-05-06 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 2:16 copies= option Russell Coker
2014-05-04 3:27 ` Duncan
2014-05-04 7:27 ` Brendan Hide
[not found] ` <xjTK1n01B308YdQ01jTMAf>
2014-05-04 18:12 ` Duncan
2014-05-04 18:31 ` Hugo Mills
2014-05-05 2:59 ` Duncan [this message]
2014-05-06 20:13 ` Chris Murphy
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$dabcf$295111b1$f1cac574$f1f862c3@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