I had also found this article just before I saw your message. The one thing
it doesn¹t deal with, though, that would be useful for Linux on z, and for
my current Intel problem, is that the uuid¹s of all the physical volumes
will be duplicates of the current system.
This will, however, work for working with a non-cloned filesystem that
happens to have a vg name that matches the name used in your ³recovery²
system.
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OC-1-13 200 First Street SW
/ ( ) \ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
> From: "Romanowski, John (OFT)" <[EMAIL PROTECTED]>
> Reply-To: Linux on 390 Port <[email protected]>
> Date: Fri, 9 Feb 2007 12:16:23 -0500
> To: <[email protected]>
> Conversation: Renaming an LVM volume group...
> Subject: Re: Renaming an LVM volume group...
>
> This might help you, See the article "Recovery of RAID and LVM2 Volumes" at
> http://www.linuxjournal.com/article/8874, in its section named " Recovering
> and Renaming the LVM2 Volume" it describes editing the duplicate vol group's
> backup file to change the volgroup's name and using vgcfgrestore -f to make
> LVM rewrite that volgroup's metatdata from the edited file. also see Listing 7
> and way way down, the "corrected listing 6".
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
