linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Dunn <andrew.g.dunn@gmail.com>
To: Peter Chacko <peterchacko35@gmail.com>
Cc: Kasper Sandberg <postmaster@metanurb.dk>,
	John Hendrikx <hjohn@xs4all.nl>,
	linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Reed Solomon coding based Raid?
Date: Sun, 29 Nov 2009 10:50:45 -0500	[thread overview]
Message-ID: <4B129855.5050702@gmail.com> (raw)
In-Reply-To: <1f808b4a0911280943x4ab781dbq28a11a2e3a77598a@mail.gmail.com>

I have been toying with the idea of an open source project to achieve a 
more generalized functional spec. than what symform has created. I was 
thinking of calling it RAINcloud (redundant array of independent nodes)

I started drawing up the requirements over the holiday weekend.

Peter Chacko wrote:
> symform, a startup create 32 parity stipes of 64 original stripes, and
> distribute the fragments in different geographies.
>
> they call it, RAID-96 And apparently reed-solomon coded.
>
> http://www.symform.com/features-benefits.aspx
>
> thanks
>
> On Sat, Nov 28, 2009 at 9:18 PM, Kasper Sandberg <postmaster@metanurb.dk> wrote:
>   
>> As far as i know, theres not support for this, however, i do believe
>> raid6 uses reed-solomon.
>>
>> On Sat, 2009-11-28 at 16:15 +0100, John Hendrikx wrote:
>>     
>>> I was wondering if there is support for a raid level where one can
>>> choose the redundancy level.  Raid 5 allows for one redundant drive,
>>> Raid 6 for two, but there's no raid level that would support arbitrary
>>> redundancy (even to the point of allowing one to add extra redundancy
>>> later on, by simply putting spare drives to immediate use).
>>>
>>> I'm just a casual Software Raid user, and have been using Raid 6 for a
>>> small 8 TB array for a few years now and I realize that there's quite
>>> some CPU overhead involved for such redundancy, but for my purposes
>>> speed is not a relevant concern (10 MB/sec is enough).
>>>
>>> --John
>>>
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>       
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>     
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>   

-- 
Andrew Dunn
http://agdunn.net


  reply	other threads:[~2009-11-29 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-28 15:15 Reed Solomon coding based Raid? John Hendrikx
2009-11-28 15:48 ` Kasper Sandberg
2009-11-28 17:43   ` Peter Chacko
2009-11-29 15:50     ` Andrew Dunn [this message]
2009-11-30 12:36       ` Goswin von Brederlow
2009-11-28 18:57 ` Keld Simonsen

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=4B129855.5050702@gmail.com \
    --to=andrew.g.dunn@gmail.com \
    --cc=hjohn@xs4all.nl \
    --cc=linux-raid@vger.kernel.org \
    --cc=peterchacko35@gmail.com \
    --cc=postmaster@metanurb.dk \
    /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).