From: Marc Bevand <bevand_m@epita.fr>
To: linux-raid@vger.kernel.org
Subject: Re: RAIDn technology
Date: Fri, 13 Feb 2004 17:48:55 +0100 [thread overview]
Message-ID: <c0iv82$q5a$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0402111508210.8702-100000@picard.science-computing.de>
Oliver Tennert wrote:
> Hello,
>
> has anybody ever heard of RAID^n technology, developed and patented by a
> company called Inostor (http://www.inostor.com)?
>
> It is designed to offer protection against the simultaneous failure of an
> arbitrary number of arbitrary disks.
>
> The pdf files publicly available on their homepage states that the
> algorithms used by them to implement an m+n RAID system (m data disks, n
> redundancy disks) are NOT the well-known Reed-Solomon codes as e.g.
> described in a well-known paper by J. Plank.
This paper is [1]. But AFAIK it describes only Vandermonde-based
Reed-Solomon codes, not Cauchy-based ones.
> Does anybody have a notion how RAID^n works? Their algorithms used seem to
> hold a regular US patent.
RAID^n is nothing more than FEC (Forward Error Correction). Any erasure
code can be used to implement FEC:
- Cauchy-based Reed-Solomon codes
- Vandermonde-based Reed-Solomon codes
- Low-Density Parity-Check codes [2] (eg: Tornado Codes...)
Tornado codes are patented by Digital Fountain [3] (RFC 3453 contains a
list of the patents). Maybe Inostor uses them ?
[1] http://www.cs.utk.edu/~plank/plank/papers/CS-96-332.html
[2] http://www.cs.utk.edu/~plank/plank/papers/CS-03-510.html
[3] http://www.digitalfountain.com
--
Marc Bevand
prev parent reply other threads:[~2004-02-13 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 14:20 RAIDn technology Oliver Tennert
2004-02-13 7:10 ` Dominik Kubla
2004-02-13 7:37 ` Oliver Tennert
2004-02-13 16:48 ` Marc Bevand [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='c0iv82$q5a$1@sea.gmane.org' \
--to=bevand_m@epita.fr \
--cc=linux-raid@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).