From: Goswin von Brederlow <goswin-v-b@web.de>
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: Mon, 01 Feb 2010 16:15:37 +0100 [thread overview]
Message-ID: <87r5p556na.fsf@frosties.localdomain> (raw)
In-Reply-To: <alpine.DEB.1.10.1002011440550.31777@uplift.swm.pp.se> (Mikael Abrahamsson's message of "Mon, 1 Feb 2010 14:42:26 +0100 (CET)")
Mikael Abrahamsson <swmike@swm.pp.se> writes:
> On Mon, 1 Feb 2010, Guy Watkins wrote:
>
>> I have always read that drives remap on failed write.
>> But have not read anything new in 2+ years.
>
> Yes, failed write is one thing, I agree that this happens. The
> question was if there is going to be re-map if there is a read that
> "was hard to do because it took several attemps before it succeeded".
>
> My experience is that it doesn't.
Why should it remap? The drive should frist rewrite the pattern to
refresh the bits and only when that fails a remap is required.
It is true that drives do not remap on FAILED reads but that means reads
so broken the ECC can not repair them. Simple bit errors that ECC can
repair the OS never sees. So maybe you just never had a rewrite of a bit
error give a write error?
MfG
Goswin
next prev parent reply other threads:[~2010-02-01 15:15 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 [this message]
2010-02-01 16:28 ` Mikael Abrahamsson
2010-02-01 20:30 ` Richard Scobie
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=87r5p556na.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox