From: Peter Benie <peterb@chiark.greenend.org.uk>
To: Andrew Clayton <andrew@sol-1.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Log your dead hard disk drives here
Date: Mon, 21 Apr 2003 12:51:39 +0100 [thread overview]
Message-ID: <16035.56139.893197.189080@chiark.greenend.org.uk> (raw)
In-Reply-To: <1050891929.1091.29.camel@alpha.digital-domain.net>
Andrew Clayton writes:
> On Mon, 2003-04-21 at 02:48, Barry K. Nathan wrote:
> > On Mon, Apr 21, 2003 at 01:09:54AM +0100, Andrew Clayton wrote:
> > > http://digital-domain.net/fscked-disk/
> >
> > What does your site do that the StorageReview.com Reliability Survey
> > doesn't? (i.e., the SR.com survey has been around for a while, why do we
> > need another?)
>
> Perhaps we don't, I wasn't aware of the above site. Looking at it
> though, mine is obviously much more to the point and is targeting one
> specific area, in that it is just logging drive failures.
I'm not convinced that you are collecting enough information to get
useful statistics, in particular, you lack any data about drives that
haven't failed yet.
Suppose that there are two vendors sell drives with identical
characteristics, one of which sells twice as many drives as the
other. In your statistics, you will give the appearance that the more
popular drive performs less well because you see twice as many
failures.
A better approach would be for people to register their drives with
you when they are new, and then to inform you when the drive fails or
is otherwise disposed of. The problem here would be to keep track of
the drives to ensure that failures really do get logged.
Peter
prev parent reply other threads:[~2003-04-21 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 0:09 Andrew Clayton
2003-04-21 1:48 ` Barry K. Nathan
2003-04-21 2:25 ` Andrew Clayton
2003-04-21 11:51 ` Peter Benie [this message]
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=16035.56139.893197.189080@chiark.greenend.org.uk \
--to=peterb@chiark.greenend.org.uk \
--cc=andrew@sol-1.demon.co.uk \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®