From: Jaap Crezee <jaap@jcz.nl>
To: Giovanni Tessore <giotex@texsoft.it>
Cc: linux-raid@vger.kernel.org
Subject: Re: read errors corrected
Date: Sun, 16 Jan 2011 09:33:25 +0100 [thread overview]
Message-ID: <4D32AD55.1040502@jcz.nl> (raw)
In-Reply-To: <4D318C46.7060204@texsoft.it>
On 01/15/11 13:00, Giovanni Tessore wrote:
> On 12/30/2010 05:41 PM, James wrote:
> As I know, Reallocated_Sector_Ct is the most meaningful SMART parameter related
> to disk sectors health.
> Also check for Current_Pending_Sector (sector that gave read on error and has
> not been reallocated yet).
> The values of your disks seems quite safe at the moment.
> Be proactive if the value grows in short time.
I wouldn't be too happy with more than 0 relocated- and/or pending sectors:
I replace these disks at once. Never had any problems with warranty about more
then 0 sectors relocated. It seems manufacturers use the same values....
regards,
Jaap Crezee
next prev parent reply other threads:[~2011-01-16 8:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 3:20 read errors corrected James
2010-12-30 5:24 ` Mikael Abrahamsson
2010-12-30 16:33 ` James
2010-12-30 16:44 ` Roman Mamedov
2010-12-30 16:51 ` James
2010-12-30 17:59 ` Ryan Wagoner
2010-12-30 18:03 ` James
2010-12-30 9:15 ` Neil Brown
[not found] ` <AANLkTik2+Gk1XveqD=crGMH5JshzJqQb_i77ZpOFUncB@mail.gmail.com>
2010-12-30 16:35 ` James
2010-12-30 23:12 ` Neil Brown
2010-12-31 1:48 ` James
2010-12-31 1:56 ` Guy Watkins
2010-12-31 2:08 ` Neil Brown
2010-12-30 10:13 ` Giovanni Tessore
2010-12-30 16:41 ` James
2011-01-15 12:00 ` Giovanni Tessore
2011-01-16 8:33 ` Jaap Crezee [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-30 20:19 Richard Scobie
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=4D32AD55.1040502@jcz.nl \
--to=jaap@jcz.nl \
--cc=giotex@texsoft.it \
--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).