All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Urlichs <matthias@urlichs.de>
To: linux-raid@vger.kernel.org
Subject: Re: Re-map disk sectors in userspace when rewriting after read errors
Date: Tue, 15 Sep 2009 07:29:18 +0000 (UTC)	[thread overview]
Message-ID: <h8nfoe$n8p$3@ger.gmane.org> (raw)
In-Reply-To: alpine.LFD.2.00.0909150810510.5083@sbhezbfg.of5.nffheflf.cev

On Tue, 15 Sep 2009 08:13:08 +0100, Alex Butcher wrote:

> IME, discs don't remap after read errors, only on writes.

Some may remap after recoverable read errors. However, the RAID code
does (I assume - see below) rewrite the data -- which the disk happily 
acknowledges  -- only to report the very same error next time that spot's 
being read. :-(

> Are you sure that refresh-writes triggered by read errors are expected
> behaviour of md's RAID5/6 mode?

Not 100%, no -- but recovering the data but otherwise ignoring the error 
(other than increment the error counter) would be a level of foolishness 
I won't assume of the RAID code's authors.

-- 
Matthias Urlichs


  reply	other threads:[~2009-09-15  7:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15  6:23 Re-map disk sectors in userspace when rewriting after read errors Matthias Urlichs
2009-09-15  6:45 ` berk walker
2009-09-15  7:23   ` Matthias Urlichs
2009-09-15  7:13 ` Alex Butcher
2009-09-15  7:29   ` Matthias Urlichs [this message]
2009-09-15  7:37     ` Alex Butcher
2009-09-15 10:48       ` Matthias Urlichs
2009-09-16  9:41         ` Goswin von Brederlow
2009-09-16 13:13           ` Matthias Urlichs
2009-09-18  8:17             ` Majed B.
2009-09-18  8:28               ` Robin Hill
2009-09-18  9:57                 ` Majed B.
2009-09-18 10:22                   ` Robin Hill
2009-09-18 10:52                     ` Majed B.
2009-09-18 11:15                       ` Robin Hill
2009-09-18 11:35               ` Matthias Urlichs
2009-09-18 17:44                 ` John Robinson
2009-09-18 18:02                   ` Greg Freemyer
2009-09-18 20:13                     ` Majed B.
2009-10-02 13:55                       ` Bill Davidsen
2009-09-15 10:40 ` Majed B.
2009-09-15 10:52   ` Matthias Urlichs
2009-09-15 11:03     ` Majed B.
2009-09-15 17:02       ` Majed B.
2009-09-15 18:05         ` Matthias Urlichs
2009-09-15 18:14           ` Majed B.
2009-09-15 18:44             ` Matthias Urlichs
2009-09-16  9:31               ` Majed B.
2009-09-16  9:44                 ` Matthias Urlichs
2009-09-16  9:52                   ` Majed B.
2009-09-16 13:05                     ` Alex Butcher
2009-09-16 10:00                   ` Robin Hill
2009-09-16 10:07                     ` Majed B.

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='h8nfoe$n8p$3@ger.gmane.org' \
    --to=matthias@urlichs.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 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.