From: Dan Christensen <jdc@uwo.ca>
To: linux-raid@vger.kernel.org
Subject: Re: "raid" versions of hard drives for software raid?
Date: Wed, 02 Jul 2008 16:54:30 -0400 [thread overview]
Message-ID: <87tzf8ovll.fsf@uwo.ca> (raw)
In-Reply-To: 486BE720.3090507@redhat.com
Brendan Conoboy <blc@redhat.com> writes:
> Dan Christensen wrote:
>> I'm looking at either the Western Digital 500G RE2 drives or the cheaper
>> 500G SE16 drives. I have read that for use with a hardware raid card,
>> the RE2 drives are more appropriate, and I'm wondering if the same is
>> true for software raid.
>
> It's a mechanical property- vibration tolerance and whatnot. No
> difference between software and hardware raid in this sense.
The difference that is most commonly described, and that I should have
highlighted, is TLER: Time-Limited Error Recovery. Apparently, the SE16
drives can take a long time to recover from an error (up to two minutes,
I believe), and hardware raid controllers can kick the drives out of the
array when it would instead be better for the drive to return a
read/write error and let the raid controller deal with it.
My question is really whether this logic applies to linux software raid.
One other point is that I also read that TLER can be enabled and
disabled for both SE16 and RE2 drives using Windows software. Not sure
if it runs under wine. See
http://www.hardforum.com/archive/index.php/t-1285254.html
Dan
next prev parent reply other threads:[~2008-07-02 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 20:30 "raid" versions of hard drives for software raid? Dan Christensen
2008-07-02 20:37 ` Brendan Conoboy
2008-07-02 20:51 ` Justin Piszcz
2008-07-02 21:30 ` Brendan Conoboy
2008-07-02 20:54 ` Dan Christensen [this message]
2008-07-03 14:34 ` Dan Christensen
2008-07-03 16:06 ` Roger Heflin
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=87tzf8ovll.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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 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.