From: Dexter Filmore <Dexter.Filmore@gmx.de>
To: linux-raid@vger.kernel.org
Subject: Too much ECC?
Date: Thu, 9 Nov 2006 15:30:55 +0100 [thread overview]
Message-ID: <200611091530.56024.Dexter.Filmore@gmx.de> (raw)
I just ran smartctl -d ata on my sATA disks (Samsung) and got these raw
values:
195 Hardware_ECC_Recovered 3344107
195 Hardware_ECC_Recovered 2786896
195 Hardware_ECC_Recovered 617712
195 Hardware_ECC_Recovered 773986
Looking at a 5 year old 40GB Maxtor that's not been cooled too well I see "3"
as the raw value.
Should I be worried or am I just not properly reading this?
Dex
--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------
http://www.stop1984.com
http://www.againsttcpa.com
next reply other threads:[~2006-11-09 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 14:30 Dexter Filmore [this message]
2006-11-09 16:50 ` Too much ECC? Gabor Gombas
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=200611091530.56024.Dexter.Filmore@gmx.de \
--to=dexter.filmore@gmx.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).