[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: copying lvm with the same name

On Thu, Mar 19, 2009 at 5:10 AM, Dr. Michael J. Chudobiak
<mjc avtechpulse com> wrote:
> Frank Cox wrote:
>> It looks like the machine can see the second drive and the lvm that's on
>> it
>> /dev/sdb2, but it has the same VolGroup name as /dev/sda2.
> Yes, this is common and annoying. Here is the guide that I followed when it
> happened to me:
> http://www.whoopis.com/howtos/linux_lvm_recovery.html
> I filed bug 461682 (https://bugzilla.redhat.com/show_bug.cgi?id=461682),
> requesting that the default volume names not be so generic - they now
> incorporate the hostname, so this problem should be much less common in
> F11+.
> - Mike

The instructions from the link do work.

The one thing I would add is that when you try to rename the VG, it may
complain of active volumes in it and bail out.

I did this exercise: rename my *system* disk's VG from VG00 to KEPLER.
This is done entirely within the LiveCD environment.
The VG name is arbitrary, name it anything you prefer.

In my system disk I have a separate /boot and a VG with /, swap, /var,
/usr, /usr/local, /tmp and /home.

**Boot with a LiveCD

You cannot change the VG name on a running system disk.
Trying to rename the VG when LVs are still active, results in an error
saying that there are active LVs in the VG.

Do "lvs" --notice that one of the LV Attributes (Attr) is "a" for active.

**Turn off the swap partition
  The LiveCD mounts the swap image and doesn't let go of it.

	# swapoff -a
	# lvchange -an /dev/VG00/swapLV (type in your own device name)

**Deactivate all LVs
  The LV name is whatever name is under the LV column.
	# lvchange -an /dev/VG00/<LV

This is where you use the reference[1] to edit the initrd image file.

[1] http://www.whoopis.com/howtos/linux_lvm_recovery.html

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]