Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Gabor Gombas <gombasg@sztaki.hu>
Cc: Brendan Conoboy <synk@swcp.com>, 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: Thu, 20 Apr 2006 11:24:48 -0400	[thread overview]
Message-ID: <1145546688.26292.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20060420152208.GF27744@boogie.lpds.sztaki.hu>

On Thu, 2006-04-20 at 17:22 +0200, Gabor Gombas wrote:
> On Wed, Apr 19, 2006 at 02:16:10PM -0400, Ming Zhang wrote:
> 
> > 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;
> 
> The mirror should be created without persistent superblocks (obviously),
> but --build does not seem to allow RAID1.
> 
> > * 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.
> 
> The process seems rather fragile. If I created a RAID5 array to protect
> my data I most certainly would not like to perform so much steps where I
> can mess up.

it can be be script and then little chance to get failed.


or if i understand current raid5 bitmap right. u can remove the disk X
from raid, then do a dd from disk X to Y, and then add disk Y to raid.
then bitmap can handle the rsync with a much less cost.




> 
> Gabor
> 


  reply	other threads:[~2006-04-20 15:24 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
2006-04-20 15:22         ` Gabor Gombas
2006-04-20 15:24           ` Ming Zhang [this message]
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=1145546688.26292.11.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=Dexter.Filmore@gmx.de \
    --cc=gombasg@sztaki.hu \
    --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