linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: berk walker <berk.walker@verizon.net>
To: TJ Harrell <systemloc@earthlink.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Hard drive Reliability?
Date: Wed, 19 May 2004 21:13:38 -0400	[thread overview]
Message-ID: <40AC0642.7060502@verizon.net> (raw)
In-Reply-To: <00b801c43e04$5c6dfd80$0201a8c0@windows>

TJ Harrell wrote:

>    I've never bought Seagate. Seagate was horribly unreliable in earlier
>times, 10 years ago, or so. I buy WD exclusively now because it is the only
>IDE drive I can get a 3 year warranty on. I've never had the problems with
>them that other people have expressed, but I don't hold high expectations,
>either.
>    I have read that the bearings used in current WD drives tend to wear
>faster at higher operating temperatures. New fluid bearings are supposedly
>less sensitive to this problem, though.
>    In any case, it seems that IDE drives are designed as throwaway drives,
>constructed as cheaply as possible. Servers generally use only SCSI. SCSI
>drives in general are manufactured better because servers require it, and
>customers are willing to pay for it. IDE equipment will not be manufactured
>as well because the market is unwilling to pay the price premium for
>quality. The market is too competetive in the desktop market. Most buyers
>don't know about quality, and buy on price. Consequently, drive prices are
>marginalized, and quality becomes of less importance.
>
>
>-
>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
>
>  
>
as hard core (read Linux) users rarely turn their systems off, wouldn't 
air-bearings be cheap and long life?

b-

  reply	other threads:[~2004-05-20  1:13 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
2004-05-20  0:49         ` TJ Harrell
2004-05-20  1:13           ` berk walker [this message]
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=40AC0642.7060502@verizon.net \
    --to=berk.walker@verizon.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=systemloc@earthlink.net \
    /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).