From: Asdo <asdo@shiftmail.org>
To: Giovanni Tessore <giotex@texsoft.it>
Cc: linux-raid@vger.kernel.org
Subject: Re: feature suggestion to handle read errors during re-sync of raid5
Date: Sat, 30 Jan 2010 22:09:41 +0100 [thread overview]
Message-ID: <4B64A015.6080904@shiftmail.org> (raw)
In-Reply-To: <4B6471A1.2070407@texsoft.it>
Giovanni Tessore wrote:
> I supposed that modern hard drives' firmware would recover and
> relocate dying sectors by its own (using smart and other techs), and
> that the OS gets read errors only when the drive is actually in very
> bad shape and can't cope with the problem, and it's time to trash it.
The disk must find the dying sector somehow.
It will certainly find it if you scrub the array often, and at that time
relocate it (by itself or by MD means). If the disk is very smart (I'm
not sure how many disks really do this) it can relocate during read, if
it finds that the sector has a partial read error which is still
correctable with the internal reed-solomon algorithm. Otherwise it will
report the read error to Linux and MD will regenerate parity and write
over the sector. At that point the sector will be relocated.
I'm not sure SMART test performs a surface scan so I would rely on MD
scrubs for that.
> Having the OS recover and rewrite the sectors makes me feel back in
> the past, when under DOS we used PCTools and other utilities to do
> this recovery stuff on ST-506 drives .... and this works well on raid,
> but in sinlge disk configuration, shouldn't these be data loss?
The OS rewrites the sector ONLY if the disk is in a raid setup.
Otherwise how could it guess the data that should be in that sector, if
the disk itself cannot?
next prev parent reply other threads:[~2010-01-30 21:09 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
2010-02-02 11:06 ` John Robinson
2010-01-30 21:09 ` Asdo [this message]
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=4B64A015.6080904@shiftmail.org \
--to=asdo@shiftmail.org \
--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).