topic Re: vgimport warnings in Operating System - HP-UX

vgimport warnings

Roy Schauwecker — Tue, 18 Nov 2003 18:01:28 GMT

I'm receiving the following warnings when importing a volume group:

Warning: Logical Volume number "61" found on physical volume not found in "/tmp/vgx070.map".
Warning: Logical Volume number "62" found on physical volume not found in "/tmp/vgx070.map".

The logical volume numbers are not in the .map files. What up with that?

If I do a ll on /dev/vgx070, I find the following:
brw-r----- 1 root sys 64 0x460043 Nov 18 13:41 lvol070119
brw-r----- 1 root sys 64 0x46003d Nov 18 13:41 lvol61
brw-r----- 1 root sys 64 0x46003e Nov 18 13:41 lvol62
crw-r----- 1 oracle dba 64 0x460001 Nov 18 13:41 rlvol070001

Note the lvol61 and lvol62...these are the guys the vgimport is complaining about.

If I do a pvdisplay -v on the device, I find the following in the listing:

00178 current /dev/vgx070/lvol070060 00001
00179 current /dev/vgx070/lvol070060 00002
00180 current ??? 00000
00181 current ??? 00001
00182 current ??? 00002
00183 current ??? 00003
00184 current ??? 00004
00185 current ??? 00005
00186 current ??? 00000
00187 current ??? 00001
00188 current ??? 00002
00189 current ??? 00003
00190 current ??? 00004
00191 current ??? 00005
00192 current /dev/vgx070/lvol070061 00000
00193 current /dev/vgx070/lvol070061 00001

It's probably all very clear to someone but it certainly has me confused. Yes, I've done a vgexport on vgx070 before trying to import.

My apolagies fo such a long post. Just wanted to throw in as much detail as possible.

Re: vgimport warnings

Michael Tully — Tue, 18 Nov 2003 18:14:57 GMT

Looks to me that the rlvol61 and rlvol62 device files are missing. You will need to re-create these.

Re: vgimport warnings

Roy Schauwecker — Tue, 18 Nov 2003 18:34:53 GMT

Actually, I have no idea what lvol61 and lvol62 are even doing there or where they're coming from. vgx070 is active on another box, there is no "lvol61" or "lvol62". Only when I transfer the .map file to a new server and try to do the import do I run into the problem. I have lvol070001 through lvol070119 associated with vgx070.

They appear at the end of my lvol listing.

lvol070001
.
.
lvol070114
lvol070115
lvol070116
lvol070117
lvol070118
lvol070119
lvol61
lvol62
rlvol070001
rlvol070002
rlvol070003
rlvol070004

Re: vgimport warnings

Sunil Sharma_1 — Wed, 19 Nov 2003 00:39:51 GMT

Hi,
In my observation the source of your problem is
1.Somebody created lvol61 and lvol62 and insted of removing it using lvremove command, deleted device files of lvol61 and lvol62.

you just try to create device file of lvol61 and lvol62 using mksf or mknod command, if you want exact syntex of command just post the output of ll /dev/vgx070 .

after creating the device file you should not get error "???" in pvdisplay command.

then you can remove lvol61 and lvol62 using lvremove and export the volume group.

it will not give you error.

Sunil

Re: vgimport warnings

Joe Short — Thu, 20 Nov 2003 14:23:49 GMT

Try running "pvdisplay -v /dev/dsk/cXtXdX" on the disks involved. It will list the lovols on the disks, so you micht be able to see if those volumes actually exist.

Re: vgimport warnings

Roy Schauwecker — Thu, 20 Nov 2003 15:08:40 GMT

Joe, if you look at the top of the thread you can seem my output from the pvdisplay -v.
note the ???

I was actually able to resolve the problem by following Michael and Sunil's advice on creating the device file. The problem for me was that the lvol61 and lvol62 wern't appearing on the server where my volume group was active. They only appeared on the servers where I had imported the volume group ...using the .map from the server where the VG was active.

I ended up exporting my active volume group and then importing from the existing map file...they now appeared on the server where the volume group was active. Once I reached that point I did the lvremove, recreated my .maps, moved them out to my other servers...all is good

Thanks for the help.