From: Goswin von Brederlow <goswin-v-b@web.de>
To: Guy Watkins <linux-raid@watkins-home.com>
Cc: 'Bill Davidsen' <davidsen@tmr.com>,
'Goswin von Brederlow' <goswin-v-b@web.de>,
linux-raid@vger.kernel.org
Subject: Re: Requesting replace mode for changing a disk
Date: Sun, 10 May 2009 09:02:24 +0200 [thread overview]
Message-ID: <877i0pe8zj.fsf@frosties.localdomain> (raw)
In-Reply-To: <4019EAB86E8342028374C6968D6D67E2@m5> (Guy Watkins's message of "Sat, 9 May 2009 22:20:07 -0400")
"Guy Watkins" <linux-raid@watkins-home.com> writes:
> If the disk is suspect, I would expect read errors!
> If you have 1 bad block on the suspect disk, this process will fail.
> If the logic was built-in to md, then any read errors while replacing could
> be recovered from another disk or disks.
That is actualy a good point. I didn't even think of that.
It would require a true replace mode in all raid levels though and not
just internally starting a raid1.
MfG
Goswin
next prev parent reply other threads:[~2009-05-10 7:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 22:15 Requesting replace mode for changing a disk Goswin von Brederlow
2009-05-09 11:41 ` John Robinson
2009-05-09 23:07 ` Bill Davidsen
2009-05-10 1:22 ` Goswin von Brederlow
2009-05-10 2:20 ` Guy Watkins
2009-05-10 7:02 ` Goswin von Brederlow [this message]
2009-05-10 14:33 ` Bill Davidsen
2009-05-10 15:55 ` Guy Watkins
2009-05-13 1:21 ` Leslie Rhorer
2009-05-13 3:27 ` Goswin von Brederlow
2009-05-13 4:36 ` Neil Brown
2009-05-13 7:37 ` Goswin von Brederlow
2009-05-13 11:02 ` Neil Brown
2009-05-14 10:44 ` David Greaves
2009-05-14 12:00 ` Neil Brown
2009-05-13 4:31 ` Neil Brown
2009-05-13 4:37 ` SandeepKsinha
2009-05-13 4:54 ` Neil Brown
2009-05-13 5:07 ` SandeepKsinha
2009-05-13 5:21 ` NeilBrown
2009-05-13 5:31 ` SandeepKsinha
2009-05-13 10:51 ` Neil Brown
2009-05-13 7:28 ` Goswin von Brederlow
-- strict thread matches above, loose matches on Subject: below --
2009-05-13 4:08 Sandeep K Sinha
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=877i0pe8zj.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=linux-raid@watkins-home.com \
/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