linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: maarten van den Berg <maarten@vbvb.nl>
To: linux-raid@vger.kernel.org
Subject: Re: Hard drive Reliability?
Date: Thu, 20 May 2004 01:53:21 +0200	[thread overview]
Message-ID: <200405200153.21371.maarten@vbvb.nl> (raw)
In-Reply-To: <200405192226.i4JMQLB16952@www.watkins-home.com>

On Thursday 20 May 2004 00:26, Guy wrote:
> >I would also concur.  I had a Western Digital that failed after 10
> >months.  Western Digital sent me another one that failed in exactly 10
> >months again.  I didn't want to send it in to get yet another piece of
> >WD junk.  So, lesson learned to stay away form WD drives; correct or not.
> >
> >Sevatio
>
> ==========================================================================
>
> I had problems with Maxtor.  So, lesson learned to stay away form Maxtor
> drives; correct or not.
>
> My friend had problems with IBM.
>
> Who's left?  I like Seagate, for now.
>
> A few years ago HP and EMC were using Seagate drives in their big disk
> arrays.  I am sure they have stats and know which drives are good.

Hm, I somehow seriously doubt that, if and when you're talking about _brands_. 
However, I strongly feel that certain _series_ are indeed better or worse 
than others.  But that only helps big manufacturers; by the time we need to 
buy a new drive the serie either doesn't exist anymore, is overhauled to 
reduce cost, or has been transfered from plant Y in Taiwan to plant X in 
China. (not that I imply anything by naming countries, they're examples) 

The tricky part, especially for manufacturers, is that they only know after 
the fact if they chose their drive brand / model wisely.  Only after a year 
or so they can see how many returns they've had, and by that time it's too 
late to change anything about it.

Maarten

-- 
Yes of course I'm sure it's the red cable. I guarante[^%!/+)F#0c|'NO CARRIER


  reply	other threads:[~2004-05-19 23:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 19:58 Hard drive Reliability? John Lange
2004-05-19 20:49 ` Måns Rullgård
2004-05-19 21:28   ` Sevatio
2004-05-19 22:02     ` John Lange
2004-05-19 22:42       ` jim
2004-05-19 22:26     ` Guy
2004-05-19 23:53       ` maarten van den Berg [this message]
2004-05-20  0:49         ` TJ Harrell
2004-05-20  1:13           ` berk walker
2004-05-20  6:39           ` Måns Rullgård
2004-05-19 23:44     ` maarten van den Berg
2004-05-19 22:04 ` berk walker
2004-05-19 22:18 ` Guy
2004-05-19 23:40   ` maarten van den Berg
2004-05-20  0:34     ` Guy
2004-05-20  1:46       ` John Lange
2004-05-20 22:27       ` Russ Price
2004-05-20 15:51     ` Sevatio
2004-05-20  4:39 ` Mark Hahn
2004-05-20  7:15   ` John Lange
2004-05-20 12:15     ` Mark Hahn
2004-05-20 13:26       ` jim
2004-05-20 13:31       ` John Lange
2004-05-20 14:20         ` Mark Hahn
2004-05-20 13:32       ` Tim Grant
2004-05-20 14:38         ` Robin Bowes
2004-05-22  5:15           ` Brad Campbell
2004-05-24 13:25             ` Frank van Maarseveen
2004-05-24 18:35               ` Brad Campbell
2004-05-24 22:38                 ` maarten van den Berg
  -- strict thread matches above, loose matches on Subject: below --
2004-05-20 13:54 Cress, Andrew R

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=200405200153.21371.maarten@vbvb.nl \
    --to=maarten@vbvb.nl \
    --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).