From: Ming Zhang <mingz@ele.uri.edu>
To: Brendan Conoboy <synk@swcp.com>
Cc: Shai <shaibn@gmail.com>, Dexter Filmore <Dexter.Filmore@gmx.de>,
linux-raid@vger.kernel.org
Subject: Re: replace disk in raid5 without linux noticing?
Date: Wed, 19 Apr 2006 14:16:10 -0400 [thread overview]
Message-ID: <1145470570.8608.100.camel@localhost.localdomain> (raw)
In-Reply-To: <44467654.2060903@swcp.com>
On Wed, 2006-04-19 at 10:41 -0700, Brendan Conoboy wrote:
> Ming Zhang wrote:
> >> Why can't you just mark that drive as failed, remove it and hotadd a
> >> new drive to replace the failed drive?
> >
> > because background rebuild is slower than disk to disk copy, since his
> > disk is still fully functional.
>
> Wouldn't it be great if every disk in a RAID volume were in its own way
> a degraded RAID1 device without a mirror? Then when any drive started
> generating recoverable errors and warnings a mirror could be allocated
> without any downtime. You can certainly generate a layout like this
> manually, but it would be nice to have that sort of feature out of the
> box (and without the performance hit!). This would help a great deal in
> a situation such as Dexter's.
is this possible?
* stop RAID5
* set a mirror between current disk X and a new added disk Y, and X as
primary one (which means copy X to Y to full sync, and before this ends,
only read from X); also this mirror will not have any metadata or mark
on existing disk;
* add this mirror to RAID5
* start RAID5;
... mirror will continue copy data from X to Y, once end
* stop RAID5
* split mirror
* put DISK Y back to RAID5
* restart RAID5.
since this is a mirror, all metadata are same. it will be even greater
if no need to stop raid5 to do this.
may MD already can do this, but I do not know.
>
> -Brendan (synk@swcp.com)
next prev parent reply other threads:[~2006-04-19 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 14:31 replace disk in raid5 without linux noticing? Dexter Filmore
2006-04-19 16:31 ` Shai
2006-04-19 17:03 ` Ming Zhang
2006-04-19 17:41 ` Brendan Conoboy
2006-04-19 18:16 ` Ming Zhang [this message]
2006-04-20 15:22 ` Gabor Gombas
2006-04-20 15:24 ` Ming Zhang
2006-04-21 18:23 ` Dexter Filmore
2006-04-21 22:25 ` Carlos Carvalho
2006-04-22 15:08 ` Martin Cracauer
2006-04-22 17:48 ` Carlos Carvalho
2006-04-23 16:43 ` Martin Cracauer
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=1145470570.8608.100.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=Dexter.Filmore@gmx.de \
--cc=linux-raid@vger.kernel.org \
--cc=shaibn@gmail.com \
--cc=synk@swcp.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;
as well as URLs for NNTP newsgroup(s).