linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harry Mangalam <hjm@tacgi.com>
To: linux-raid@vger.kernel.org
Subject: Re: More tales of horror from the linux (HW) raid crypt
Date: Wed, 22 Jun 2005 13:16:33 -0700	[thread overview]
Message-ID: <200506221316.33178.hjm@tacgi.com> (raw)
In-Reply-To: <42B9BCF6.1010206@h3c.com>

Thanks for the note - I'd also be interested in what drives people people use 
that seem to be robust and which are having problems.  The 3ware tech that I 
spoke to recommended the WD-SD series, but a local senior sysadmin has warned 
his entire dept off WD drives for the reasons I've mentioned.  He rec'ed 
Seagate (5 year warr) and Hitachi.  So far the only good thing that I can say 
about WD is that their return policy has been relatively smooth (tho they 
smoothly keep returning bad drives :( )

I personally buy IBM (now Hitachi I think) and Seagate and have always avoided 
WD as being cheap and cheesy.  5 years ago when I was a sysadmin, I was 
replacing WD at probably 5 times the rate of anything else.  It was probably 
strongly influenced by the fact that more people were using them than the 
others but I don't think I've ever had an IBM or seagate 3.5" die (have a 
teetering stack of working ones that just got too small to bother with).  I 
figured that since WD was still in business (tho seeming always on the verge 
of going bust) their quality must have improved, but maybe not.

Happy to be contradicted.  If there's a 'Consumer's Reports' for HD 
reliability on the web, I couldn't find it.  Maybe it's time to set one up - 
with SMART disk records, it's possible to get more reliable runtime records 
and data than just the usual single point or small data set that individuals 
can provide (and you can bet that most vendors aren't going to make their 
failures public..).

Perhaps something like the CDDB, where a you can run an applet on a cronjob 
that will upload your disk's SMART data cache to a remote DB on a regular 
basis, so the millions of disks out there can be profiled.  Hmmm - sounds 
like a good undergrad project. Did someone say Summer of Code? 
(http://code.google.com/summerofcode.html)

hjm




On Wednesday 22 June 2005 12:33 pm, Mike Hardy wrote:
> Not that I wish bad luck on anyone, but I always enjoy reading about
> problems others have had and how they solved them, so I don't have to
> learn the hard way. Hopefully your situation gets sorted out.

-- 
Cheers, Harry
Harry J Mangalam - 949 856 2847 (vox; email for fax) - hjm@tacgi.com 
            <<plain text preferred>>

  reply	other threads:[~2005-06-22 20:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-18 11:47 when does it become faulty disk Raz Ben-Jehuda(caro)
2005-06-19 19:10 ` Molle Bestefich
2005-06-20  6:43   ` raz ben jehuda
2005-06-20  7:55     ` Molle Bestefich
2005-06-20 10:09       ` raz ben jehuda
2005-06-20 13:45   ` Michael Tokarev
2005-06-20 15:35     ` raz ben jehuda
2005-06-21  1:53 ` More tales of horror from the linux (HW) raid crypt Harry Mangalam
2005-06-22 19:33   ` Mike Hardy
2005-06-22 20:16     ` Harry Mangalam [this message]
2005-06-22 20:38       ` Jure Pecar
2005-06-22 21:33         ` Harry Mangalam
2005-06-22 23:15           ` SMART, was " Konstantin Olchanski
2005-06-22 23:32             ` Harry Mangalam
2005-06-22 23:35             ` Mike Hardy
2005-06-22 21:09       ` Brad Dameron
2005-06-22 21:43         ` Harry Mangalam
2005-06-22 22:00           ` Ming Zhang
2005-06-22 22:11             ` John Madden
2005-06-22 22:26               ` Ming Zhang
2005-06-23  0:20               ` bdameron
2005-06-22 22:45             ` Harry Mangalam
2005-06-22 23:05               ` Ming Zhang
2005-06-23  0:25               ` bdameron
2005-06-23  0:14             ` bdameron
2005-06-23  0:49               ` Ming Zhang
2005-06-23  3:05                 ` Guy
2005-06-23 12:31                   ` Ming Zhang
2005-06-23 13:03                     ` Guy
2005-06-23 13:17                       ` Andy Smith
2005-06-23 13:19                       ` Ming Zhang
2005-06-22 23:54       ` Jon Lewis
2005-06-22 20:54     ` Dan Stromberg
2005-06-22 21:15       ` Brad Dameron

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=200506221316.33178.hjm@tacgi.com \
    --to=hjm@tacgi.com \
    --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).