linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: Mark Hahn <hahn@mcmaster.ca>
Cc: linux-raid@vger.kernel.org
Subject: Re: PATA/SATA Disk Reliability paper
Date: Sun, 25 Feb 2007 14:22:28 +0300	[thread overview]
Message-ID: <200702251422.28079.a1426z@gawab.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702241716130.28888@coffee.psychology.mcmaster.ca>

Mark Hahn wrote:
> > In contrast, ever since these holes appeared, drive failures became the
> > norm.
>
> wow, great conspiracy theory!

I think you misunderstand.  I just meant plain old-fashioned mis-engineering.

> maybe the hole is plugged at
> the factory with a substance which evaporates at 1/warranty-period ;)

Actually it's plugged with a thin paper-like filter, which does not seem to 
evaporate easily.

And it's got nothing to do with warranty, although if you get lucky and the 
failure happens within the warranty period, you can probably demand a 
replacement drive to make you feel better.

But remember, the google report mentions a great number of drives failing for 
no apparent reason, not even a smart warning, so failing within the warranty 
period is just pure luck.

> seriously, isn't it easy to imagine a bladder-like arrangement that
> permits equilibration without net flow?  disk spec-sheets do limit
> this - I checked the seagate 7200.10: 10k feet operating, 40k max.
> amusingly -200 feet is the min either way...

Well, it looks like filtered net flow on wd's.

What's it look like on seagate?

> >>    Doe anyone rememnber that you had to let you drives acclimate to
> >> your machine room for a day or so before you used them.
> >
> > The problem is, that's not enough; the room temperature/humidity has to
> > be controlled too.  In a desktop environment, that's not really
> > feasible.
>
> 5-90% humidity, operating, 95% non-op, and 30%/hour.  seems pretty easy
> to me.  in fact, I frequently ask people to justify the assumption that
> a good machineroom needs tight control over humidity.  (assuming, like
> most machinerooms, you aren't frequently handling the innards.)

I agree, but reality has a different opinion, and it may take down that 
drive, specs or no specs.

A good way to deal with reality is to find the real reasons for failure.  
Once these reasons are known, engineering quality drives becomes, thank GOD, 
really rather easy.


Thanks!

--
Al


  reply	other threads:[~2007-02-25 11:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18 18:50 PATA/SATA Disk Reliability paper Richard Scobie
2007-02-19 11:26 ` Al Boldi
2007-02-19 21:42   ` Eyal Lebedinsky
2007-02-20 12:15     ` Al Boldi
2007-02-22 22:27       ` Nix
2007-02-22 22:30         ` Nix
2007-02-22 23:30         ` Stephen C Woods
2007-02-23 18:22           ` Al Boldi
2007-02-24 22:27             ` Mark Hahn
2007-02-25 11:22               ` Al Boldi [this message]
2007-02-25 17:40                 ` Mark Hahn
     [not found]                   ` <200702252057.22963.a1426z@gawab.com>
2007-02-25 19:58                     ` Mark Hahn
2007-02-25 21:07                       ` Al Boldi
2007-02-25 22:14                         ` Mark Hahn
2007-02-25 22:46                           ` Benjamin Davenport
2007-02-25 23:58                             ` Mark Hahn
2007-02-27 19:21                   ` Bill Davidsen
2007-02-25 19:02               ` Richard Scobie
2007-02-27 19:06           ` Bill Davidsen
2007-02-26 14:15   ` Mario 'BitKoenig' Holbe
2007-02-26 17:46     ` Al Boldi
2007-02-20  3:03 ` H. Peter Anvin

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=200702251422.28079.a1426z@gawab.com \
    --to=a1426z@gawab.com \
    --cc=hahn@mcmaster.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 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).