VG issue

[TTr]

1. Verify the correct device files in ioscan. The map file and the saved config file do not mean anything during a vgimport.

2. The error "vg10 is still active" indicates that the vg10 already exists when you try the vgimport. Probably a bad /etc/lvmtab. Try deleting /etc/lvmtab and vgscan to recreate it.

3. If the error persists after /etc/lvmtab is recreated, disocnnect the vg10 PVs and repeat deleting and recreating lvmtab. This way the vg10 PVs will not get vg-scanned.

4. If the lvmtab is recreated successfully, try importing the vg10 PVs again.

5. Try pvdisplay on one of the vg10 PVs. Do you see anything bad or is it normal? Do NOT run pvcreate on those PVs.

[Rahul Khare]

tried your suggestion. After disconnecting the devices, they were not scanned in vgscan but still vg10 was showing as being "active".

Seems like its getting picked up irrespective of removing the lvmtab file.

Is there any way that I could mark this volume group to be de-active and then re-import the same?

[whiz_kid]

try this

vgexport -p -s -m vg10.map -f vg10.pvmap vg10

vgexport vg10

mkdir /dev/vg10
mknod /dev/vg10 group c 64 0xXX0000 (replace XX with suitable major value)

vgimport -s -m vg10.map vg10

post the output.

[Ramesh S]

Hi

Try this one also,

The most likely cause is a duplicate minor number in the group file. Check the group file also

# ll /dev/*/group

Thanks & Regards

Ramesh

[TTr]

I noticed in /etc/lvmtab, the vg00 has 3 PV that have target numbers t8, t9, t10 with dual paths c0 and c1. Might those be 3 of the 7 PVs of vg10 and that is why you can not restore vg10?

Go to /etc/lvmconf and post the output of
"strings vgXX.conf" for each vg. Preferably you should get an original vgXX.conf from the ignite tape because the current /etc/lvmconf is probably overwritten by ypur recent vgscan/vgimport attempts. To get an original copy of any folder or file from the ignite tape use

# mt -t /dev/rmt/0m rew
# mt -t /dev/rmt/0mn fsf 1 (must use "mn" here)
# cd /tmp
# tar xvf /dev/rmt/0mn etc/lvmconf