From: Andre Noll <maan@systemlinux.org>
To: David Brown <david.brown@hesbynett.no>
Cc: linux-raid@vger.kernel.org
Subject: Re: Safely swapping a disk in a RAID456
Date: Sat, 1 Oct 2011 17:51:42 +0200 [thread overview]
Message-ID: <20111001155142.GG30935@systemlinux.org> (raw)
In-Reply-To: <j679h5$g42$1@dough.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
On Sat, Oct 01, 16:53, David Brown wrote:
> On 30/09/11 18:28, Andre Noll wrote:
> >On Fri, Sep 30, 17:42, martin f krafft wrote:
> >>Does anyone have any ideas?
> >
> >Create a 2-disk Raid1 (with external metadata) containing the disk
> >you'd like to replace and the replacement disk.
> >
> >And yes, it would be great if md provided an easier way to do this.
> >
>
> That would be "hot replace", which is quite high up on the md/mdadm
> "things to do" list.
>
> <http://neil.brown.name/blog/20110216044002#2>
Thanks for the pointer. I wonder if it would be useful to have an
md-aware dd command which could read from an md device and output
only the contents of one component. I.e. it would give the same result
as dd if=/dev/component-device of=/dev/new-disk if there are no read
errors but would redirect failed reads to the working devices.
This should be easy to implement as it avoids the complexity mentioned
in Neil's blog posting. Moreover, it could be written purely in user
space and would work on any kernel version. The price to pay is of
course that the array needs to be r/o during the operation.
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-10-01 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 15:42 Safely swapping a disk in a RAID456 martin f krafft
2011-09-30 16:06 ` Rudy Zijlstra
2011-09-30 17:07 ` Andre Noll
2011-09-30 16:28 ` Andre Noll
2011-10-01 14:53 ` David Brown
2011-10-01 15:51 ` Andre Noll [this message]
2011-09-30 18:02 ` John Robinson
2011-10-01 3:38 ` Danny Rawlins
2011-10-01 10:32 ` Asdo
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=20111001155142.GG30935@systemlinux.org \
--to=maan@systemlinux.org \
--cc=david.brown@hesbynett.no \
--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).