9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Joshua Wood <josh@utopian.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ata drive capabilities
Date: Wed, 26 Dec 2007 08:22:12 -0800	[thread overview]
Message-ID: <43095ABE-E9E6-4F60-8B7A-6485C3645F99@utopian.net> (raw)

> the google paper shows a 40% afr for the first 6 months after some
> smart errors appear.  (unfortunately they don't do numbers for
> a simple smart status.)

Yes, and I rather mischaracterized the google paper's comments on  
SMART. A reread (I first read them a few months ago) shows the above.  
Further, the CMU paper even references the google study on the SMART  
subject:

``They find that [ ... ] the value of several SMART counters  
correlate highly with failures.''

So SMART appears a little less dumb. I'd say meets the better than  
nothing criterion.

> from my understanding of how google do things, loosing a drive just
> means they need to replace it.  so it's cheeper to let drives fail.
> on the other hand, we have our main filesystem raided on an aoe
> appliance.  suppose that one of those raids has two disks showing
> a smart status of "will fail".  in this case i want to know the  
> elevated
> risk and i will allocate a spare drive to replace at least one of the
> drives.
>
> i guess this is the long way of saying, it all depends on how painful
> loosing your data might be.  if it's painful enough, even a poor tool
> like smart is better than nothing.
>
I agree (plus I was just wrong about SMART at first), though I do  
think your example above is about preventing downtime, not so much  
data loss (Even without smart entirely, and all the disks come up  
corrupt, we're all backed up within some acceptable window, right?)


> what a pity! it would have been so great to have had
> an objective assessment of reliability by manufacturer.
>
Since the CMU thing found no difference between disk *types*, I  
wonder if it might be that there's little difference between  
manufacturers either -- instead the difference is in manufacturing,  
i.e., `vintage' & the like.

> i've found it really quite hard to find useful data to
> indicate how reliable a drive might be.
>

I think Fig. 2, Sec. 4.2 of the CMU paper relates to that; the  
`infant mortality' of manufactured mechanical parts isn't captured in  
MTTF -- but IDEMA is apparently going to solve this by replacing the  
single MTTF number that I don't quite understand with 4 different  
MTTF numbers, one for each `phase' of a disk's life.

--
Josh




             reply	other threads:[~2007-12-26 16:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26 16:22 Joshua Wood [this message]
2007-12-26 18:14 ` erik quanstrom
  -- strict thread matches above, loose matches on Subject: below --
2007-12-27  9:01 Joshua Wood
2007-12-27 15:15 ` Brantley Coile
2007-12-27  6:22 Joshua Wood
2007-12-27  7:28 ` erik quanstrom
2007-12-26  7:44 Joshua Wood
2007-12-26 13:18 ` roger peppe
2007-12-26 18:15   ` erik quanstrom
2007-12-25 21:40 Christian Kellermann
2007-12-25 21:48 ` Pietro Gagliardi
2007-12-25 23:59 ` erik quanstrom
2007-12-26  6:31   ` ron minnich
2007-12-26 13:10     ` erik quanstrom
2007-12-26 19:52       ` Christian Kellermann
2007-12-26 20:13         ` andrey mirtchovski
2007-12-27 18:12           ` Christian Kellermann
2007-12-26 23:58         ` Robert William Fuller
2007-12-27  2:34         ` erik quanstrom

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=43095ABE-E9E6-4F60-8B7A-6485C3645F99@utopian.net \
    --to=josh@utopian.net \
    --cc=9fans@cse.psu.edu \
    /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).