From: Xavier Nicollet <nicollet@jeru.org>
To: Hugo Mills <hugo@carfax.org.uk>,
tom@drdabbles.us, Gareth Pye <gareth@cerberos.id.au>,
linux-btrfs@vger.kernel.org
Subject: Re: Balance RAID10 with odd device count
Date: Wed, 22 Feb 2012 09:56:27 +0100 [thread overview]
Message-ID: <20120222085627.GS30450@jeru.org> (raw)
In-Reply-To: <20120221075422.GG5350@carfax.org.uk>
Le 21 February 2012 ? 07:54, Hugo Mills a =E9crit:
> Some time ago, I proposed the following scheme:
>=20
> <n>C<m>S<p>P
>=20
> where n is the number of copies (suffixed by C), m is the number o=
f
> stripes for that data (suffixed by S), and p is the number of parity
> blocks (suffixed by P). Values of zero are omitted.
>=20
> So btrfs's RAID-1 would be 2C, RAID-0 would be 1CnS, RAID-5 would
> be 1CnS1P, and RAID-6 would be 1CnS2P. DUP would need a special
> indicator to show that it wasn't redundant in the face of a whole-dis=
k
> failure: 2CN
Seems clear. However, is the S really relevant ?
It would be simpler without it, wouldn't it ?
--=20
Xavier Nicollet
--
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:[~2012-02-22 8:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 0:35 Balance RAID10 with odd device count Tom Cameron
2012-02-21 0:45 ` Wes
2012-02-21 0:51 ` Wes
2012-02-21 1:07 ` Tom Cameron
[not found] ` <CA+WRLO9BgqE+CwCUNgjwjVFyjDDp94SBX_EbdVciHUd0jpUqWQ@mail.gmail.com>
2012-02-21 1:59 ` Tom Cameron
2012-02-21 2:46 ` Gareth Pye
2012-02-21 7:54 ` Hugo Mills
2012-02-22 8:56 ` Xavier Nicollet [this message]
2012-02-22 10:22 ` Hubert Kario
2012-02-22 11:09 ` Hugo Mills
2012-02-21 1:07 ` Hugo Mills
2012-02-21 1:13 ` Tom Cameron
2012-02-21 1:21 ` Hugo Mills
2012-02-22 11:48 ` Duncan
2012-02-21 1:27 ` Wes
2012-02-21 1:31 ` Hugo Mills
2012-02-21 1:16 ` Liu Bo
2012-02-21 1:22 ` Hugo Mills
2012-02-21 1:13 ` 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=20120222085627.GS30450@jeru.org \
--to=nicollet@jeru.org \
--cc=gareth@cerberos.id.au \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=tom@drdabbles.us \
/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.