From: Erik Mouw <erik@harddisk-recovery.com>
To: Mattias Wadenstein <maswan@acc.umu.se>
Cc: Bill Davidsen <davidsen@tmr.com>,
Linux Raid List <linux-raid@vger.kernel.org>
Subject: Re: RAID5E
Date: Wed, 31 May 2006 16:54:48 +0200 [thread overview]
Message-ID: <20060531145448.GD24826@harddisk-recovery.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0605311626240.18452@montezuma.acc.umu.se>
On Wed, May 31, 2006 at 04:27:54PM +0200, Mattias Wadenstein wrote:
> On Wed, 31 May 2006, Bill Davidsen wrote:
> >Where I was working most recently some systems were using RAID5E (RAID5
> >with both the parity and hot spare distributed). This seems to be highly
> >desirable for small arrays, where spreading head motion over one more
> >drive will improve performance, and in all cases where a rebuild to the
> >hot spare will avoid a bottleneck on a single drive.
> >
> >Is there any plan to add this capability?
>
> What advantage does that have over raid6? You use exactly as many drives
> (n+2), with the disadvantage of having to do a rebuild without parity when
> a drive fails and a raid failure at a double disk failure.
Advantage:
- Easier to calculate the checksum (RAID5 XOR instead of a generator
polynome with RAID6)
- Higher throughput compared to standard RAID5
- Actually uses the hot spare
Disadvantage:
- Doesn't protect against double disk failures, but RAID5 also doesn't
Note that you could also do RAID6E.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2006-05-31 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 13:47 RAID5E Bill Davidsen
2006-05-31 14:27 ` RAID5E Mattias Wadenstein
2006-05-31 14:54 ` Erik Mouw [this message]
2006-05-31 19:03 ` RAID5E Bill Davidsen
2006-06-01 1:13 ` RAID5E Neil Brown
2006-06-12 13:50 ` RAID5E Bill Davidsen
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=20060531145448.GD24826@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=maswan@acc.umu.se \
/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.