9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ata drive capabilities
Date: Wed, 26 Dec 2007 08:10:05 -0500	[thread overview]
Message-ID: <fb64e063d19fa84fb20128916ed54ce7@quanstro.net> (raw)
In-Reply-To: <13426df10712252231u167ae5c2k616534728b97e338@mail.gmail.com>

On Wed Dec 26 01:33:14 EST 2007, rminnich@gmail.com wrote:
> On Dec 25, 2007 6:59 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> >(we have a drive
> > in the lab that smart declares will fail any minute now.  it's been
> > this way for 2 years.)
> 
> From everything I've seen, SMART has zero correlation with real
> hardware issues -- confirmed by a discussion with someone at a big
> search company. SMART is dumb.

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.)

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.

- erik


  reply	other threads:[~2007-12-26 13:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2007-12-26  7:44 Joshua Wood
2007-12-26 13:18 ` roger peppe
2007-12-26 18:15   ` erik quanstrom
2007-12-26 16:22 Joshua Wood
2007-12-26 18:14 ` erik quanstrom
2007-12-27  6:22 Joshua Wood
2007-12-27  7:28 ` erik quanstrom
2007-12-27  9:01 Joshua Wood
2007-12-27 15:15 ` Brantley Coile

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=fb64e063d19fa84fb20128916ed54ce7@quanstro.net \
    --to=quanstro@quanstro.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).