From: Ming Zhang <mingz@ele.uri.edu>
To: dean gaudet <dean@arctic.org>
Cc: "Paul M." <paul@gpmidi.net>, linux-raid@vger.kernel.org
Subject: Re: how to clone a disk
Date: Sat, 11 Mar 2006 19:54:06 -0500 [thread overview]
Message-ID: <1142124846.27020.59.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0603111641320.21574@twinlark.arctic.org>
On Sat, 2006-03-11 at 16:47 -0800, dean gaudet wrote:
> On Sat, 11 Mar 2006, Ming Zhang wrote:
>
> > On Sat, 2006-03-11 at 16:31 -0800, dean gaudet wrote:
> > > if you fail the disk from the array, or boot without the failing disk,
> > > then the event counter in the other superblocks will be updated... and the
> > > removed/failed disk will no longer be considered an up to date
> > > component... so after doing the ddrescue you'd need to reassemble the
> > > raid5. i'm not sure you can convince md to use the bitmap in this case --
> > > i'm just not familiar enough with it.
> >
> > i am little confused here. then what the purpose of that bitmap for? is
> > not that bitmap is for a component temporarily out of place and thus out
> > of sync a bit?
>
> hmm... yeah i suppose that is the purpose of the bitmap... i haven't used
> bitmaps yet though... so i don't know which types of events they protect
> against. in theory what you want to do sounds like it should work though,
> but i'd experiment somewhere safe first.
yes, need to see if can find bitmap usage and purpose from archive here
or google.
>
> -dean
prev parent reply other threads:[~2006-03-12 0:54 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
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 [this message]
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=1142124846.27020.59.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=dean@arctic.org \
--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).