All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Scobie <richard@sauce.co.nz>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: 'Linux RAID' <linux-raid@vger.kernel.org>
Subject: Re: feature suggestion to handle read errors during re-sync of  raid5
Date: Tue, 02 Feb 2010 09:30:07 +1300	[thread overview]
Message-ID: <4B6739CF.8050808@sauce.co.nz> (raw)
In-Reply-To: <alpine.DEB.1.10.1002011726570.31777@uplift.swm.pp.se>

Mikael Abrahamsson wrote:

> Since the drive has ECC, it would be interesting to see the amount of
> read errors ECC has corrected. Would also be interesting to know if the
> drive will rewrite a sector if it's ECC corrected, so that ECC doesn't
> have to kick in next time (or if they're actually operating in so narrow
> margins that they actually use the ECC constantly because the s/n ratio
> is bad and that this is part of the design).

I guess this is manufacturer and model specific, but looking smartd 
output from a representative (as in similar errors etc to others of the 
same model) Seagate SCSI drive, they are not rewriting on ECC:

Error counter log:
            Errors Corrected by           Total   Correction 
Gigabytes    Total
                EEC          rereads/    errors   algorithm 
processed    uncorrected
            fast | delayed   rewrites  corrected  invocations   [10^9 
bytes]  errors
read:    2205106        0         0   2205106    2205106      18342.407 
           0
write:         0        0         0         0          0       3831.185 
           0


Regards,

Richard

  reply	other threads:[~2010-02-01 20:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-30 12:37 feature suggestion to handle read errors during re-sync of raid5 Mikael Abrahamsson
2010-01-30 17:51 ` Giovanni Tessore
2010-01-30 19:04   ` John Robinson
2010-01-30 21:33     ` Mikael Abrahamsson
2010-01-30 22:04       ` Asdo
2010-01-30 22:25         ` Mikael Abrahamsson
2010-01-31 16:17       ` John Robinson
2010-01-31 16:34         ` Asdo
2010-01-31 18:04           ` Goswin von Brederlow
2010-01-31 17:56         ` Mikael Abrahamsson
2010-02-01  1:30           ` Roger Heflin
2010-02-01  7:15             ` Mikael Abrahamsson
2010-02-01 13:33               ` Guy Watkins
2010-02-01 13:42                 ` Mikael Abrahamsson
2010-02-01 15:15                   ` Goswin von Brederlow
2010-02-01 16:28                     ` Mikael Abrahamsson
2010-02-01 20:30                       ` Richard Scobie [this message]
2010-02-02 11:06                       ` John Robinson
2010-01-30 21:09   ` Asdo
2010-01-30 18:59 ` Goswin von Brederlow

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=4B6739CF.8050808@sauce.co.nz \
    --to=richard@sauce.co.nz \
    --cc=linux-raid@vger.kernel.org \
    --cc=swmike@swm.pp.se \
    /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.