vgimport error !

[Helen French]

Hi All,

I am trying to import a VG after a cold install (upgrade) HP-UX 11.0. The vgname is vg02, and has one lvol1 and is mirrored. Now when I am trying this command:

# vgimport -m /tmp/vg02.map -s -p -v /dev/vg02

Beginning the import process on Volume Group "/dev/vg02".
Logical volume "/dev/vg02/lvol1" has been successfully created with lv number 3.
Warning: Logical Volume number "1" found on physical volume not found in "/tmp/vg02.map".
Logical volume "/dev/vg02/lvol1" has been successfully created with lv number 1.
Warning: Logical Volume number "2" found on physical volume not found in "/tmp/vg02.map".
Logical volume "/dev/vg02/lvol2" has been successfully created with lv number 2.
Volume group "/dev/vg02" has been successfully created.


Is it going to create a problem while I do the 'vgimport' without -p ? Mirror/UX is already installed on the server.

Thanks!
Shiju

[Donna Powell]

Unfortunately, I have never been able to use the vgexport and vgimport with success. If you only have one lvol in the volume group. I would recommend recreating it over again. Because even if you do get it to come back it sounds like it may be corrupted.

Donna Powell-Berry

[S.K. Chan · Accepted solution]

Have you tried without the -s option but put in the PV-paths in the arguments, run in preview mode and see if there is any error ?

You seems to do everything right, -s option gives you the flexibility of not having to specify the PV-paths and yet it still complain, I assume you used -s also in your vgexport command ?

[Helen French]

Hi S.K Chan,

I would love to assign 100 points to you !

The vgimport without -s option worked, but not in a proper manner ! However I did that and activated the VG and I can see the lvol1 is mirrored. This was the error:

# vgimport -m /tmp/vg02.map -v /dev/vg02 /dev/dsk/c1t13d0 /dev/dsk/c0t13d0
Beginning the import process on Volume Group "/dev/vg02".
Logical volume "/dev/vg02/VGID" has been successfully created with lv number 1.
Logical Volume is not defined on any physical volume. "/dev/vg02/e026d534db273c" is missing Physical Volumes.
Logical volume "/dev/vg02/lvol1" has been successfully created with lv number 3.
Volume group "/dev/vg02" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating the volume group.

Now I don't know from where the VGID came ? Is this another error ? I think I can safely remove this lv from the vg (?)

Thanks again .. points to follow

Shiju

[Darrell Allen]

Hi Shiju,

I'm not familiar with the -s option but what I just read makes it sound as though the disk(s) found by using -s were not the one(s) you formerly used for your vg02.

Is it possible for you to specify the disks you want instead of using -s? Do you need the sharable option?

Darrell

[Helen French]

Hi Darrell,

Thanks for the heads up !

1) The disks which found by -s option are the same which I specified. I did check this when I exported tha VG.

2) I don't need the sharable option, but I was assuming that using -s is a good choice while vgimport/export.

3) I think it is possible to specify the disks withou using -s, because it worked for me now.

Any idea about the new logical volume- VGID ? Does this is an effect of using -s in vgexport, but not using with vgimport ? Any issues if I delete this ?

Thanks!
Shiju

[Darrell Allen]

Wish I could help you with that. Sorry.

I use the -m option for a mapfile with vgexport and vgimport. I also use the -f option to let the system create a list of PVs for the VG and I don't have to type them in.

Darrell

[S.K. Chan]

Hi Shiju, I'm glad it worked out, though not what should be expected out of it. I have not been using -s option for all the vgexport experience that I've done. The reason is I don't need it to be shared plus when I import it, I'd prefer to defined my PV-path. This is just a personal choice. "-s" is simplified way and it create an additional field called VGID in your map file and later uses that VGID in the vgimport process which allow you NOT NEEDING to specify the PV-path. If you vgexport without the "-s" option akll the map file contain is the name of the lvol, no VGID, so later to import it, you got to define the PV-paths. Try this ,, you'll know what I mean ...
# vgexport -m mapfile -s -p /dev/vg00
# vgexport -m mapfile2 -p /dev/vg00
and take a look at both map files.

[S.K. Chan]

So ( man I'm long winded ) in your case since your map file got "VGID" and some id numbers next to it, when you vgimport without -s option it'll think VGID and "that number" are lvol names and hence try to create these lvols for you which you can then safely remove later.

[Helen French]

Hi,

Thanks everybody ! It worked fine for me. Here is the conclusion:

1) The 'VGID' logical volume created because the vgimport was executed without -s option ( as S.K. Chan said)

2) I have removed the VGID with lvremove:

# lvremove /dev/vg02/VGID
# vgchange -a n vg02
# vgchange -a y vg02

and looks fine now.

3) The reason why it was not working with '-s' option ( I think): I could find some mismatches in the 'vgdisplay' output which I took before the upgrade. The lv defenitions (current lv, open lv etc) were not matching, and this might have been created a problem while importing the vg with -s. The logical volume number was 3, but there was only one LV.

Thanks for all your time and inputs.

Have a good weekend !
Shiju