From: Gil <gil@fooplanet.com>
To: Christopher Smith <csmith@nighthawkrad.net>
Cc: gsslist+linuxraid@anthropohedron.net, linux-raid@vger.kernel.org
Subject: Re: Best way to achieve large, expandable, cheap storage?
Date: Fri, 21 Oct 2005 09:48:04 -0700 [thread overview]
Message-ID: <43591BC4.7090903@fooplanet.com> (raw)
In-Reply-To: <435871A4.8040304@nighthawkrad.net>
Christopher Smith wrote:
> Gregory Seidman wrote:
>
>> You should at least read the following before using RAID5. You
>> can agree or disagree, but you should take the arguments into
>> account:
>>
>> http://www.miracleas.com/BAARF/RAID5_versus_RAID10.txt
> For example, his article suggests that "partial media failure" is
> a problem that would only affect RAID5, when really it would
> negatively impact any RAID system (your newly-synced mirror isn't
> much good if half the data that just got mirrored to it was
> corrupted, nor is the speed boost from RAID0 very helpful if half
> the data is corrupted). I'm also not sure about his claims of
> RAID3 & 4 "always" checking parity - that sounds like a
> vendor-specific implementation (and while I'm not a developer, I
> fail to see why a RAID5 implementation couldn't be made to do the
> same).
The partial media failure problem described here is exactly why it's
important to run smartmontools in combination with your RAID array
of any level. By running regular checks of the disk surface you can
know well ahead of time that you're going to have trouble. in
practice this more than mitigates the risk of partial media failure.
http://smartmontools.sourceforge.net/
--Gil
next prev parent reply other threads:[~2005-10-21 16:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 13:20 Best way to achieve large, expandable, cheap storage? Robin Bowes
2005-09-30 13:29 ` Robin Bowes
2005-09-30 18:28 ` Brad Dameron
2005-09-30 19:20 ` Dan Stromberg
2005-09-30 18:16 ` Gregory Seidman
2005-09-30 18:34 ` Andy Smith
2005-10-02 4:36 ` Christopher Smith
2005-10-02 7:09 ` Tyler
2005-10-03 3:19 ` Christopher Smith
2005-10-03 16:33 ` Sebastian Kuzminsky
2005-10-04 4:09 ` Christopher Smith
2005-10-20 10:23 ` Robin Bowes
2005-10-20 11:19 ` Gregory Seidman
2005-10-20 11:41 ` Robin Bowes
2005-10-21 4:42 ` Christopher Smith
2005-10-21 16:48 ` Gil [this message]
2005-10-21 20:08 ` Robin Bowes
2005-10-21 4:40 ` Christopher Smith
-- strict thread matches above, loose matches on Subject: below --
2005-10-27 19:12 Andrew Burgess
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=43591BC4.7090903@fooplanet.com \
--to=gil@fooplanet.com \
--cc=csmith@nighthawkrad.net \
--cc=gsslist+linuxraid@anthropohedron.net \
--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).