From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: Can uuid of raid array be changed?
Date: Tue, 19 Apr 2005 08:56:08 +0200 [thread overview]
Message-ID: <20050419065608.GA29247@percy.comedia.it> (raw)
In-Reply-To: <42645952.1050504@advocap.org>
On Mon, Apr 18, 2005 at 08:05:22PM -0500, John McMonagle wrote:
>Luca Berra wrote:
>
>>On Sun, Apr 17, 2005 at 05:04:13PM -0500, John McMonagle wrote:
>>
>>>Need to duplicate some computers that are using raid 1.
>>>
>>>I was thinking of just adding adding an extra drive and then moving
>>>it to the new system. The only problem is the clones will all have
>>>the same uuids. If at some later date the drives got mixed up I
>>>could see a possibilities for disaster. Not exactly likely as the
>>>computers will be in different cities.
>>>
>>>Is there a way to change the uuid if a raid array?
>>>Is it really worth worrying about?
>>>
>>you can recreate the array, this will not damage existing data.
>>
>>L.
>>
>Thanks
>
>I'll try it.
>I suspect I'll find out real quick but do you need to a
>--zero-superblock on all devices making the raid arrays?
NO
>Will this damage the lvm2 superblock info?
>Probably a good idea to do a vgcfgback just to be safe..
NO
the idea is after you cloned the drive, create a new array with the
force flag and using as components the cloned disk and the magic word
"missing", this will create a new degraded array and won't touch any
data.
you can then hotadd a new drive to this array, it will fill the slot
used by the "missing" keyword.
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
prev parent reply other threads:[~2005-04-19 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 22:04 Can uuid of raid array be changed? John McMonagle
2005-04-18 7:13 ` Luca Berra
2005-04-19 1:05 ` John McMonagle
2005-04-19 6:56 ` Luca Berra [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=20050419065608.GA29247@percy.comedia.it \
--to=bluca@comedia.it \
--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).