LVM and VxVM

VG Import of a LVM Version 2.0 Volume Group

 
John Ford_1
Occasional Contributor

VG Import of a LVM Version 2.0 Volume Group

I have no idea why, but I created two volume groups with Version 2.0. Here is my problem. I have data that I replicate via SRDF on a SYMM to my DR site. I've been able to do vgimports all of the time because the sybase guys use named raw partitions(lv's). Anyway, so I created a vgmap file with the following command. vgexport -v -m vg05.map -s /dev/vg05 and the same with vg6.

Here is the output of the VG05.map file(which is different then what I'm used to seeing).
MAPFILE02
VGID A0000000000000001Fri Feb 27 20:36:40 200975b7f04f-6bf3-11dd-ae35-663e139c07
cb
1 sybase

Anyway I'm able to do a vgimport, AND I found the data being populated in the /etc/lvmtab_p file(took me a bit to find that).

strings /etc/lvmtab_p
/dev/vg05
A0000000000000001Fri Feb 27 20:36:40 200975b7f04f-6bf3-11dd-ae35-663e139c07cb
/dev/dsk/c2t15d5

But every time I attempt to activate the drive with a vgchange I get the following error.

vgchange -a y /dev/vg05
vgchange: Couldn't activate volume group "/dev/vg05":
Quorum not present, or some physical volume(s) are missing.

I've attempted to tell it to activate without the quorum but still get the same error.

vg05 is a volume group with only one 9 gig lun in it on the other side, so I'm not missing anything. And I can clearly see the disks exist and size.

So what am I missing here?

Please help!
3 REPLIES 3
Steven E. Protter
Exalted Contributor

Re: VG Import of a LVM Version 2.0 Volume Group

Shalom,

Can you back up the data, destroy and rebuild the volume group using a version you are more familiar with, followed by data restore?

I know its a pain, but downgrading a volume group does not seem possible.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Michael Steele_2
Honored Contributor

Re: VG Import of a LVM Version 2.0 Volume Group

HI

a) check your old lvmtabs for another disk

b) pvdisplay disk and verify what vg is written to it

c) vgreduce -f /dev/vg

The is a discrepencey between the kernel and lvmtab. Using c) will keep lvmtab, refer to what is in the kernel, and remove the difference.
Support Fatherhood - Stop Family Law
Michael Steele_2
Honored Contributor

Re: VG Import of a LVM Version 2.0 Volume Group

d) vgcfgrestore /etc/lvmconf/vg.map_old -l

Note the -l. This can also help you id the problem disk by listing out the old map file.

vgscan -p -s -a -v

-p preview
-s all pv's
-a all controllers
-v verbose

This will poll all luns accessible to the box and build a preview of a new lvmtab. Note: Don't use without -p preview unless you want to overwrite your current lvmtab.
Support Fatherhood - Stop Family Law