volume group on top of md raid array dissappears after reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lvm2 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
In a fresh install of Jaunty Alpha 6, the system has two identical 120GB ata hard drives. during the boot process I create 4 identical partitions and add them to Raid arrays:
md0 is /boot with 210MB Raid 1
md1 is swap with 1GB Raid 0
md2 is / with 4GB Raid 1
md3 is physical volume for LVM using the rest of the space in Raid 1
I created a volume group called 'vgdata' with md3
After a reboot, the volume group is missing. Running the following commands find the the volume group and appear to complete successfully:
sudo pvscan
sudo vgscan
sudo vgchange -ay vgdata
sudo vgmknodes
but there is still no /dev/vgkvm device created. I've tried wiping out md3 and recreating the raid device and volume group manually from the command line. After creation, I can use the volume group like normal, but it dissappears again after reboot.
This may be more of a feature request than a bug. I see now that the volume group device does not show up unless a logical volume exists on the device.
This cause a problem with virt-manager though, which is where I first noticed it. I created the volume group with the intention of adding it as a storage pool to virt-manger/ libvirt, but I am unable to do so with a blank volume group.