From: Richard Scobie <richard@sauce.co.nz>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: component growing in raid5
Date: Fri, 28 Mar 2008 11:09:08 +1300 [thread overview]
Message-ID: <47EC1B04.7040006@sauce.co.nz> (raw)
In-Reply-To: <Pine.GSO.4.64.0803261016550.15900@montezuma.acc.umu.se>
Mattias Wadenstein wrote:
>> A day or two? That's quite risky. Never mind that you get awful
>> performance for that day or two and/or a risk of data corruption.
>> Neil Brown some weeks on this mailing list expressed a very
>> cautionary thought:
>>
>> «It is really best to avoid degraded raid4/5/6 arrays when at all
>> possible. NeilBrown»
>
>
> Yes, I read that mail. I've been meaning to do some real-world testing
> of restarting degraded/rebuilding raid6es from various vendors,
> including MD, but haven't gotten around to it.
You may be interested in these results - throughput results on an 8 SATA
drive RAID6 showed average write speed went from 348MB/s to 354MB/s and
read speed 349MB/s to 196MB/s, while rebuilding with 2 failed drives.
This was with an Areca 1680x RAID controller.
http://www.amug.org/amug-web/html/amug/reviews/articles/areca/1680x/
Regards,
Richard
--
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
next prev parent reply other threads:[~2008-03-27 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 6:59 component growing in raid5 Nagy Zoltan
2008-03-23 11:24 ` Peter Grandi
2008-03-24 7:09 ` Peter Rabbitson
2008-03-24 7:09 ` Peter Rabbitson
2008-03-24 15:17 ` Nagy Zoltan
2008-03-24 15:42 ` Peter Rabbitson
2008-03-24 16:52 ` Nagy Zoltan
2008-03-25 13:06 ` Peter Grandi
2008-03-25 13:38 ` Mattias Wadenstein
2008-03-25 20:02 ` Peter Grandi
2008-03-27 20:44 ` Mattias Wadenstein
2008-03-27 22:09 ` Richard Scobie [this message]
2008-03-28 8:07 ` Mattias Wadenstein
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=47EC1B04.7040006@sauce.co.nz \
--to=richard@sauce.co.nz \
--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).