From: Paolo Ornati <ornati@fastwebnet.it>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Chr <chunkeey@web.de>, "Robert Hancock" <hancockr@shaw.ca>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Björn Steinbrink" <B.Steinbrink@gmx.de>,
"Jens Axboe" <jens.axboe@oracle.com>,
"Jeff Garzik" <jeff@garzik.org>, "Tejun Heo" <htejun@gmail.com>
Subject: Re: SATA exceptions triggered by XFS (since 2.6.18)
Date: Mon, 22 Jan 2007 09:16:05 +0100 [thread overview]
Message-ID: <20070122091605.7aadd678@localhost> (raw)
In-Reply-To: <45B40B18.4090500@gmail.com>
On Mon, 22 Jan 2007 01:53:21 +0059
Jiri Slaby <jirislaby@gmail.com> wrote:
> >> 7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 204305750
> >> 1 Raw_Read_Error_Rate 0x000f 059 049 006 Pre-fail Always - 215927244
> >> 195 Hardware_ECC_Recovered 0x001a 059 049 000 Old_age Always - 215927244
> >
> > Wow! that HDD is really in a bad condition.
>
> I don't think so, this seems to be normal for Seagate drives...
I agree.
For Chr: I don't think these big raw-numbers are counters, look at the
normalized values instead, and see that they are greater than TRESH
values (so they are good).
The meaning of raw-numbers is vendor specific.
--
Paolo Ornati
Linux 2.6.20-rc5 on x86_64
next prev parent reply other threads:[~2007-01-22 8:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 14:29 SATA exceptions triggered by XFS (since 2.6.18) Paolo Ornati
2007-01-21 16:40 ` Paolo Ornati
2007-01-21 17:32 ` Robert Hancock
2007-01-21 19:25 ` Paolo Ornati
2007-01-21 20:32 ` Chr
2007-01-22 0:54 ` Jiri Slaby
2007-01-22 8:16 ` Paolo Ornati [this message]
2007-01-22 2:46 ` Tejun Heo
2007-01-22 8:38 ` Paolo Ornati
2007-01-22 9:35 ` Tejun Heo
2007-01-22 10:02 ` Paolo Ornati
2007-01-22 10:21 ` Paolo Ornati
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=20070122091605.7aadd678@localhost \
--to=ornati@fastwebnet.it \
--cc=B.Steinbrink@gmx.de \
--cc=chunkeey@web.de \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=jirislaby@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.