From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Re: PATA/SATA Disk Reliability paper
Date: Mon, 26 Feb 2007 15:15:45 +0100 [thread overview]
Message-ID: <eruq2h$nvi$1@sea.gmane.org> (raw)
In-Reply-To: 200702191426.16567.a1426z@gawab.com
Al Boldi <a1426z@gawab.com> wrote:
> Interesting link. They seem to point out that smart not necessarily warns of
> pending failure. This is probably worse than not having smart at all, as it
> gives you the illusion of safety.
If SMART gives you the illusion of safety, you didn't understand SMART.
SMART hints *only* the potential presence or occurence of failures in
the future, it does not prove the absence of such - and nobody ever said
it does. It would even be impossible to do that, though (which is easy
to prove by just utilizing an external damaging tool like a hammer).
Concluding from that that not having any failure detector at all is
better than having at least an imperfect one is IMHO completely wrong.
regards
Mario
--
File names are infinite in length where infinity is set to 255 characters.
-- Peter Collinson, "The Unix File System"
next prev parent reply other threads:[~2007-02-26 14:15 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
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 [this message]
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='eruq2h$nvi$1@sea.gmane.org' \
--to=mario.holbe@tu-ilmenau.de \
--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).