From: Brendan Hide <brendan@swiftspirit.co.za>
To: Marc MERLIN <marc@merlins.org>, Martin <m_btrfs@ml1.co.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs and raid5 status with kernel 3.14, documentation, and howto
Date: Tue, 25 Mar 2014 10:04:52 +0200 [thread overview]
Message-ID: <533138A4.2010808@swiftspirit.co.za> (raw)
In-Reply-To: <20140325012916.GF11533@merlins.org>
On 25/03/14 03:29, Marc MERLIN wrote:
> On Tue, Mar 25, 2014 at 01:11:43AM +0000, Martin wrote:
>> There's a big thread a short while ago about using parity across
>> n-devices where the parity is spread such that you can have 1, 2, and up
>> to 6 redundant devices. Well beyond just raid5 and raid6:
>>
>> http://lwn.net/Articles/579034/
>
> Aah, ok. I didn't understand you meant that. I know nothing about that, but
> to be honest, raid6 feels like it's enough for me :)
There are a few of us who are very much looking forward to these
special/flexible RAID types - for example RAID15 (very good performance,
very high redundancy, less than 50% diskspace efficiency). The csp
notation will probably make it easier to develop the flexible raid types
and is very much required in order to better manage these more flexible
raid types.
A typical RAID15 with 12 disks would in csp notation is written as:
2c5s1p
And some would like to be able to use the exact same redundancy scheme
even with extra disks:
2c5s1p on 16 disks (note, the example is not 2c7s1p, though that would
also be a valid scheme with 16 disks being the minimum number of disks
required)
The last thread on this (I think) can be viewed here,
http://www.spinics.net/lists/linux-btrfs/msg23137.html where Hugo also
explains and lists the notation for the existing schemes.
--
__________
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
prev parent reply other threads:[~2014-03-25 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 22:56 Btrfs and raid5 status with kernel 3.14, documentation, and howto Marc MERLIN
2014-03-24 19:17 ` Martin
2014-03-24 21:52 ` Marc MERLIN
2014-03-25 1:11 ` Martin
2014-03-25 1:29 ` Marc MERLIN
2014-03-25 8:04 ` Brendan Hide [this message]
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=533138A4.2010808@swiftspirit.co.za \
--to=brendan@swiftspirit.co.za \
--cc=linux-btrfs@vger.kernel.org \
--cc=m_btrfs@ml1.co.uk \
--cc=marc@merlins.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