From: Ming Zhang <mingz@ele.uri.edu>
To: "Paul M." <paul@gpmidi.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: how to clone a disk
Date: Sat, 11 Mar 2006 17:08:11 -0500 [thread overview]
Message-ID: <1142114892.27020.7.camel@localhost.localdomain> (raw)
In-Reply-To: <dd43dcfb0603110353g1a4d51f6y9fe4caa4007b6e9c@mail.gmail.com>
On Sat, 2006-03-11 at 06:53 -0500, Paul M. wrote:
> Since its raid5 you would be fine just pulling the disk out and
> letting the raid driver rebuild the array. If you have a hot spare
yes, rebuilding is the simplest way. but rebuild will need to read all
other disks and write to the new disk. when serving some io at same
time, the rebuilding speed is not much,
but if i do a dd clone and plug it back. the total traffic is copy one
disk which can be done very fast as a fully sequential workload. with
that bitmap feature, the rsync work after plugging back is minor.
so the one disk fail window is pretty small here. right?
ming
> then that disk will automatically take over when you remove the
> failing disk.
> It would also be reasonable to simply wait for the disk to fail. When
> that happens the array will be keep running. When the disk does fail
> the system will use the hot spare to rebuild the array.
> The short answer is your way will work but it not necessarily.
> -Paul
>
> On 3/10/06, Ming Zhang <mingz@ele.uri.edu> wrote:
> > Hi folks
> >
> > I have a raid5 array that contain 4 disk and 1 spare disk. now i saw one
> > disk have sign of going fail via smart log.
> >
> > so i am trying to do this
> >
> > 1) pull that disk (A) out
> > 2) using dd to copy that disk (A) to another same one (B);
> > 3) put disk (B) back to raid5 and assume that bitmap can help me resync
> > quickly.
> >
> > now my question is
> > 1) can this achieve my goal?
> > 2) is there any better/correct way?
> >
> > thanks!
> >
> > Ming
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
next prev parent reply other threads:[~2006-03-11 22:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 0:56 how to clone a disk Ming Zhang
2006-03-11 11:53 ` Paul M.
2006-03-11 12:40 ` PFC
2006-03-11 16:55 ` Mike Hardy
2006-03-11 22:09 ` Ming Zhang
2006-03-11 23:08 ` Mike Hardy
2006-03-11 23:10 ` Ming Zhang
2006-03-11 22:08 ` Ming Zhang [this message]
2006-03-12 0:15 ` dean gaudet
2006-03-12 0:22 ` Ming Zhang
2006-03-12 0:31 ` dean gaudet
2006-03-12 0:36 ` Ming Zhang
2006-03-12 0:47 ` dean gaudet
2006-03-12 0:54 ` Ming Zhang
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=1142114892.27020.7.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=linux-raid@vger.kernel.org \
--cc=paul@gpmidi.net \
/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).