From: David Greaves <david@dgreaves.com>
To: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
Cc: linux-raid@vger.kernel.org
Subject: Re: Proactive Drive Replacement
Date: Tue, 21 Oct 2008 18:29:53 +0100 [thread overview]
Message-ID: <48FE1191.3030302@dgreaves.com> (raw)
In-Reply-To: <gdkn4n$u6p$1@ger.gmane.org>
Mario 'BitKoenig' Holbe wrote:
> David Greaves <david@dgreaves.com> wrote:
>> The main issue is that the drive being replaced almost certainly has a bad
>> block.
>
> Then, the replacement is not pro-active ;)
>
>> This block could be recovered from the raid5 set but won't be.
>
> This is what 'check' and 'repair' operations
> (/sys/block/md*/md/sync_action) can be used for.
Well, yes and no.
If I have a bad block then I could use the remaining disks to calculate data to
overwrite it. So yes.
However the overwrite may fail. So no.
If I have an md managed mirror then the overwrite will write to the new disk and
the old one. I don't care if the old one fails.
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
next prev parent reply other threads:[~2008-10-21 17:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 17:35 Proactive Drive Replacement Jon Nelson
2008-10-20 22:40 ` Mario 'BitKoenig' Holbe
2008-10-21 8:38 ` David Greaves
2008-10-21 13:05 ` Jon Nelson
2008-10-21 13:36 ` David Greaves
2008-10-21 13:50 ` David Lethe
2008-10-21 14:11 ` Mario 'BitKoenig' Holbe
2008-10-21 15:13 ` David Lethe
2008-10-21 15:30 ` Mario 'BitKoenig' Holbe
2008-10-21 19:39 ` David Greaves
2008-10-21 13:57 ` Mario 'BitKoenig' Holbe
2008-10-21 17:29 ` David Greaves [this message]
2008-10-24 5:57 ` Luca Berra
2008-10-24 8:09 ` David Greaves
2008-10-25 13:20 ` Luca Berra
2008-10-25 16:33 ` David Greaves
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=48FE1191.3030302@dgreaves.com \
--to=david@dgreaves.com \
--cc=Mario.Holbe@TU-Ilmenau.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.