From: Hugo Mills <hugo@carfax.org.uk>
To: tom@drdabbles.us
Cc: Wes <anomaly256@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Balance RAID10 with odd device count
Date: Tue, 21 Feb 2012 01:21:48 +0000 [thread overview]
Message-ID: <20120221012148.GD5350@carfax.org.uk> (raw)
In-Reply-To: <CA+Huu1E2cg5a4PWtCkN4a4qou4T++VENsLjC8=TiRPJw5tzAUA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]
On Mon, Feb 20, 2012 at 08:13:43PM -0500, Tom Cameron wrote:
> On Mon, Feb 20, 2012 at 8:07 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
> >
> > However, you can remove any one drive, and your data is fine, which
> > is what btrfs's RAID-1 guarantee is. I understand that there will be
> > additional features coming along Real Soon Now (possibly at the same
> > time that RAID-5 and -6 are integrated) which will allow the selection
> > of larger numbers of copies.
> >
>
> Is there a projected timeframe for RAID5/6? I understand it's
> currently not the development focus of the BTRFS team, and most
> organizations want performance over capacity making RAID10 the clear
> choice. But, there are still some situations where RAID6 is better
> suited (large pools of archive storage).
Rumour has it that it's the next major thing after btrfsck is out
of the door. I don't know how accurate that is. I'm just some bloke on
the Internet. :)
> Also, do we know if the RAID5/6 implementation will simply break data
> into two data objects and one or two parity objects, or will it work
> with an arbitrary number of devices? Meaning, if I have a RAID6 pool
> of 12 drives, will I get 10 data objects and two parity objects?
AFAIK, the original implementation looked something like the RAID-0
code, so if you have n drives with space for the next block group,
it'll take all n drives to use for the block group. Parity is then
allocated out of those n (with the distribution of the parity blocks
across different drives, as RAID-5 and -6 should do).
So, allocating a RAID-6 block group of width 1G on your example
12-drive machine, you will indeed end up with 10G of space in that
block group, and 2G of parity data spread across all 12 drives.
I don't know if the code that will be delivered will allow you to
set a smaller fixed-size stripe width (e.g. 4 data + 2 parity over 8
drives). If the 3-copies RAID-1 code rumour is also true, I would hope
so. Again, I'm just some bloke on the Internet...
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- I'd make a joke about UDP, but I don't know if ---
anyone's actually listening...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2012-02-21 1:21 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
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 [this message]
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=20120221012148.GD5350@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=anomaly256@gmail.com \
--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 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).