From: Bill Davidsen <davidsen@tmr.com>
To: Neil Brown <neilb@suse.de>
Cc: Dan <dan@korstad.net>, linux-raid@vger.kernel.org
Subject: Re: new features time-line
Date: Mon, 30 Oct 2006 18:19:52 -0500 [thread overview]
Message-ID: <45468898.5030506@tmr.com> (raw)
In-Reply-To: <17718.59159.519516.656790@cse.unsw.edu.au>
Neil Brown wrote:
>On Tuesday October 17, davidsen@tmr.com wrote:
>
>
>>We talked about RAID5E a while ago, is there any thought that this would
>>actually happen, or is it one of the "would be nice" features? With
>>larger drives I suspect the number of drives in arrays is going down,
>>and anything which offers performance benefits for smaller arrays would
>>be useful.
>>
>>
>
>So ... RAID5E is RAID5 using (N-1)/N of each drive (or close to that)
>and not having a hot spare.
>On a drive failure, the data is restriped across N-1 drives so that it
>becomes plain RAID5. This means that instead of having an idle spare,
>you have spare space at the end of each drive.
>
>To implement this you would need kernel code to restripe and array to
>reduce the number of devices (currently we only increase the number of
>devices).
>
>Probably not too hard - just needs code and motivation.
>
Code is not coming from me right now, but the motivation is (a) all
drives in use so better response, particularly with small arrays, and
(b) spare is being used, if it's going to have a problem it won't be
just when you need it the most.
I suppose someone will want RAID6E as well, I would probably find a use
for it, but RAID5E would suit many systems which could use a
speed+reliability boost.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-10-30 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 21:53 new features time-line Dan
2006-10-14 0:03 ` Neil Brown
2006-10-18 2:35 ` Bill Davidsen
2006-10-19 2:46 ` Neil Brown
2006-10-30 23:19 ` Bill Davidsen [this message]
[not found] <45300FC5.80806@h3c.com>
2006-10-14 0:14 ` Dan
2006-10-16 5:37 ` Neil Brown
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=45468898.5030506@tmr.com \
--to=davidsen@tmr.com \
--cc=dan@korstad.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).