From: Michael Tokarev <mjt@tls.msk.ru>
To: st0ff@npl.de
Cc: linux-raid@vger.kernel.org
Subject: Re: Feature Request
Date: Tue, 09 Feb 2010 15:28:10 +0300 [thread overview]
Message-ID: <4B7154DA.90405@msgid.tls.msk.ru> (raw)
In-Reply-To: <4B712034.1000600@gmx.net>
Stefan *St0fF* Huebner wrote:
[]
> Now imagine any RAID with some kind of redundancy, reading/writing
> data. One of the disks finds out "I cannot correctly read/write the
> requested sector", starts its error correction, hits the respective
> ERC-timeout and reports back a media error or unrecoverable error. Now
> mdraid would drop the disk.
>
> But actually the data of the sector can be recreated through the
> existing redundancy. Wouldn't it be a smart thing if the mdraid
> recreates the sector and just tried to write it again? And after a good
> amount of failed retries it may well drop the disk.
This is exactly what md layer is doing. On failed _read_ it tries to
reconstruct data from other disk drives and writes the reconstructed
data back to the drive where read failed. If the _write_ fails md will
drop the disk.
/mjt
next prev parent reply other threads:[~2010-02-09 12:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 8:43 Feature Request Stefan *St0fF* Huebner
2010-02-09 12:28 ` Michael Tokarev [this message]
2010-02-09 14:19 ` Stefan Hübner
-- strict thread matches above, loose matches on Subject: below --
2024-06-20 12:58 Clement Sello Tsetsa
2024-06-20 13:29 ` rsbecker
2016-10-27 21:55 feature request John Rood
2016-10-27 22:01 ` Stefan Beller
2016-10-27 22:05 ` John Rood
2016-10-27 22:24 ` John Rood
2016-10-27 22:27 ` Junio C Hamano
2016-10-27 22:48 ` John Rood
2016-10-27 22:51 ` Junio C Hamano
2016-10-27 23:16 ` John Rood
2016-10-27 22:30 ` Stefan Beller
2016-10-27 22:44 ` John Rood
2016-10-27 22:46 ` Junio C Hamano
2016-10-27 23:24 ` David Lang
2016-10-28 8:49 ` Johannes Schindelin
2016-10-28 12:54 ` Philip Oakley
2013-02-18 18:52 Jay Townsend
2013-02-18 19:54 ` James Nylen
2013-02-18 20:45 ` Jeff King
2013-02-19 3:26 ` Drew Northup
2013-02-19 22:27 ` Shawn Pearce
2012-10-16 11:36 Angelo Borsotti
2012-10-16 12:15 ` Andrew Ardill
2012-10-16 17:27 ` Angelo Borsotti
2012-10-16 23:30 ` Sitaram Chamarty
2012-10-17 0:00 ` Andrew Ardill
2012-10-16 13:34 ` Christian Thaeter
2008-09-09 9:49 Feature Request l5ynlwlcyku9kvaqc2jf.j.HadVabVobs
2005-04-14 16:50 feature request `VL
2005-04-14 18:18 ` Taylor, Grant
2005-04-14 18:37 ` Leonardo Rodrigues Magalhães
2005-04-14 18:52 ` Taylor, Grant
2003-08-23 7:51 Pentium 4m kernel 2.4.21 Martin Klinkigt (multimedia-test)
2003-08-23 9:49 ` Viktor Radnai
2003-08-23 10:50 ` Feature request (was: Pentium 4m kernel 2.4.21) Viktor Radnai
2003-08-26 23:10 ` Dominik Brodowski
2003-08-27 17:16 ` Feature request Viktor Radnai
2003-08-28 13:50 ` Dominik Brodowski
2003-08-28 16:04 ` Daniel Thor Kristjansson
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=4B7154DA.90405@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-raid@vger.kernel.org \
--cc=st0ff@npl.de \
/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.