From: Harry Mangalam <hjm@tacgi.com>
To: Konstantin Olchanski <olchansk@sam.triumf.ca>
Cc: linux-raid@vger.kernel.org
Subject: Re: SMART, was Re: More tales of horror from the linux (HW) raid crypt
Date: Wed, 22 Jun 2005 16:32:03 -0700 [thread overview]
Message-ID: <200506221632.03294.hjm@tacgi.com> (raw)
In-Reply-To: <20050622231513.GC23624@sam.triumf.ca>
On Wednesday 22 June 2005 4:15 pm, Konstantin Olchanski wrote:
> But does anybody know what all these SMART parameters *mean* ?!?
Yes, apparently, it's all written down:
http://smartmontools.sourceforge.net/#references
> AFAIK, only a handful of parameters ("temperature", "reallocated sectors",
> and "start stop count") seem to measure something. All the other
> stuff appears to be complete gibberish.
Yup, I agree. But the information that isn't useful doesn't negate that which
is. And the gibberish may indeed be useful once it is interpreted.
> Then for the SMART "status", it is completely useless- I had SMART
> complain about perfectly good disks ("this disk will fail soon!!!"- a few
> 120GB WDs that sometimes stop seeking, probably through overheating)
> and I had completely unusable disks (i.e. develops about 10 unreadable
> sectors per day) that SMART was perfectly happy with.
This I can't address - I've not had this experience - others can speak up
about this.
> K.O.
(and thanks again for your help on my original problem!)
--
Cheers, Harry
Harry J Mangalam - 949 856 2847 (vox; email for fax) - hjm@tacgi.com
<<plain text preferred>>
next prev parent reply other threads:[~2005-06-22 23:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 11:47 when does it become faulty disk Raz Ben-Jehuda(caro)
2005-06-19 19:10 ` Molle Bestefich
2005-06-20 6:43 ` raz ben jehuda
2005-06-20 7:55 ` Molle Bestefich
2005-06-20 10:09 ` raz ben jehuda
2005-06-20 13:45 ` Michael Tokarev
2005-06-20 15:35 ` raz ben jehuda
2005-06-21 1:53 ` More tales of horror from the linux (HW) raid crypt Harry Mangalam
2005-06-22 19:33 ` Mike Hardy
2005-06-22 20:16 ` Harry Mangalam
2005-06-22 20:38 ` Jure Pecar
2005-06-22 21:33 ` Harry Mangalam
2005-06-22 23:15 ` SMART, was " Konstantin Olchanski
2005-06-22 23:32 ` Harry Mangalam [this message]
2005-06-22 23:35 ` Mike Hardy
2005-06-22 21:09 ` Brad Dameron
2005-06-22 21:43 ` Harry Mangalam
2005-06-22 22:00 ` Ming Zhang
2005-06-22 22:11 ` John Madden
2005-06-22 22:26 ` Ming Zhang
2005-06-23 0:20 ` bdameron
2005-06-22 22:45 ` Harry Mangalam
2005-06-22 23:05 ` Ming Zhang
2005-06-23 0:25 ` bdameron
2005-06-23 0:14 ` bdameron
2005-06-23 0:49 ` Ming Zhang
2005-06-23 3:05 ` Guy
2005-06-23 12:31 ` Ming Zhang
2005-06-23 13:03 ` Guy
2005-06-23 13:17 ` Andy Smith
2005-06-23 13:19 ` Ming Zhang
2005-06-22 23:54 ` Jon Lewis
2005-06-22 20:54 ` Dan Stromberg
2005-06-22 21:15 ` Brad Dameron
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=200506221632.03294.hjm@tacgi.com \
--to=hjm@tacgi.com \
--cc=linux-raid@vger.kernel.org \
--cc=olchansk@sam.triumf.ca \
/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).