public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: nuitari@balthasar.nuitari.net (Nuitari)
Cc: venom@sns.it, linux-kernel@vger.kernel.org,
	xavier.bestel@free.fr, mark@veltzer.org
Subject: Re: Hi is this critical??
Date: Tue, 17 Sep 2002 09:02:12 +0100 (BST)	[thread overview]
Message-ID: <200209170802.g8H82CTZ000701@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0209170114580.20176-100000@balthasar.nuitari.net> from "Nuitari" at Sep 17, 2002 01:18:01 AM

> On Tue, 17 Sep 2002 venom@sns.it wrote:
> 
> > On Mon, 16 Sep 2002 jbradford@dial.pipex.com wrote:
> > 
> > >
> > > S.M.A.R.T. is useful to prove that a drive is dying, but it is not useful to prove that it is not.
> > 
> > Yes, of course, and this was exaclty what was asked here in the mail
> > from xavier that started this thread. The point is if S.M.A.R.T will
> > advice before you see seek errors messages from the kernel or not.
> 
> It never advised me before seeing problems in the kernel (I had about 5 
> drives dying running Linux machines).

Were you actually monitoring the S.M.A.R.T. information before you suspected that the drive was failing, though?

S.M.A.R.T. data is only meaningful when it's monitored over a period of time.  The actual numbers are fairly meaningless, and are bound to vary from drive to drive, but if you suddenly find that, for example, spinning up the disk is taking longer than normal, then you might suspect that there is something wrong with the motor/spindle assembly.

S.M.A.R.T. is far from being perfect, but it is another tool that we have at our disposal.  All modern discs support S.M.A.R.T. so you might as well enable it.  If nothing else, you could replace the disk after, say, 10,000 power on hours, or 2500 spin up, (wash, rinse, spin), and spin down, cycles.  I.E. Preventative maintainance.

> It should be trivial to just grep the kernel log for the error and mail it 
> to some address. 

Exactly, you can do this in user space, using tail -f and a perl script.

> Another way to prove a dead drive is (after a backup) to drop it some 
> until it made a nice broken drive sound (a very high pitch shriek) and 
> bring it to the store that sold it to you (ideally a small one as they are 
> less technically challenged then big chains).

I think they would probably say that you voided the warranty.

John.

  reply	other threads:[~2002-09-17  7:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16 20:05 2.4.19 - not a real problem raptor
2002-09-16 13:31 ` Hi is this critical?? louie miranda
2002-09-16 13:34   ` DevilKin
2002-09-16 13:37   ` venom
2002-09-16 13:47     ` Xavier Bestel
2002-09-16 14:16       ` Mark Veltzer
2002-09-16 14:14         ` Xavier Bestel
2002-09-16 15:57           ` venom
2002-09-16 23:23             ` Nuitari
2002-09-16 18:27               ` jbradford
2002-09-16 22:46                 ` venom
2002-09-17  5:18                   ` Nuitari
2002-09-17  8:02                     ` jbradford [this message]
2002-09-17  8:20                       ` Andre Hedrick
2002-09-17 10:41                         ` Alan Cox
2002-09-17 11:09                           ` Russell King
2002-09-17 11:17                             ` Alan Cox
2002-09-17 12:02                               ` Russell King
2002-09-17 12:17                                 ` jbradford
2002-09-17 12:02                               ` jbradford
2002-09-17 18:39                                 ` Bill Davidsen
2002-09-18  6:00                                 ` Daniel Berlin
2002-09-17 17:34                             ` Andre Hedrick
2002-09-17 17:54                               ` Russell King
2002-09-17 19:30                                 ` jbradford
2002-09-17 18:34                             ` Bill Davidsen
2002-09-18  5:56                             ` Daniel Berlin
2002-09-17 18:23                           ` Bill Davidsen
2002-09-16 14:43       ` Russell King
2002-09-17  8:40       ` Rogier Wolff
2002-09-17  9:03         ` jbradford
2002-09-16 14:53   ` Alan Cox
2002-10-05 12:58 ` 2.4.19 - not a real problem Adrian Bunk

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=200209170802.g8H82CTZ000701@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@veltzer.org \
    --cc=nuitari@balthasar.nuitari.net \
    --cc=venom@sns.it \
    --cc=xavier.bestel@free.fr \
    /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