From: Hubert Kario <hka@qbs.com.pl>
To: Mike Fedyk <mfedyk@mikefedyk.com>
Cc: Bart Noordervliet <bart@noordervliet.net>, linux-btrfs@vger.kernel.org
Subject: Re: Raid1 with 3 drives
Date: Fri, 5 Mar 2010 23:27:27 +0100 [thread overview]
Message-ID: <201003052327.28202.hka@qbs.com.pl> (raw)
In-Reply-To: <93cdabd21003051413m76a8babs2ab5a58c32dd9aee@mail.gmail.com>
On Friday 05 March 2010 23:13:54 Mike Fedyk wrote:
> On Fri, Mar 5, 2010 at 1:49 PM, Bart Noordervliet <bart@noordervliet.=
net>=20
wrote:
> > Maybe it's worth to consider leaving the burdened raid* terminology
> > behind and name the btrfs redundancy modes more clearly by what the=
y
> > do. For instance "-d double|triple" or "-d 2n|3n". And for raid5/6 =
"-d
> > single-parity|double-parity" or "-d n+1|n+2".
>=20
> +1
Good idea IMHO.
When we will be able to specify the redundancy modes on a file by file =
basis=20
it will make it much less confusig for the users to talk about double, =
triple =20
replication or [single|double]-parity.=20
It's a bit silly to talk about "Arrays of Disks" when we mean groups of=
=20
blocks.
--=20
Hubert Kario
QBS - Quality Business Software
ul. Ksawer=C3=B3w 30/85
02-656 Warszawa
POLAND
tel. +48 (22) 646-61-51, 646-74-24
fax +48 (22) 646-61-50
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-05 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 19:28 Raid1 with 3 drives Grady Neely
2010-03-05 19:40 ` Josef Bacik
2010-03-05 19:58 ` Chris Ball
2010-03-05 20:29 ` Grady Neely
2010-03-05 20:31 ` Josef Bacik
2010-03-05 21:49 ` Bart Noordervliet
2010-03-05 22:13 ` Mike Fedyk
2010-03-05 22:27 ` Hubert Kario [this message]
2010-03-06 1:02 ` Ravi Pinjala
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=201003052327.28202.hka@qbs.com.pl \
--to=hka@qbs.com.pl \
--cc=bart@noordervliet.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfedyk@mikefedyk.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.