Vgimport - No LVM info

[Muda Ikhsan_1]

Hi.. i want to do vgimport to new disks.

but then i got this message ?
# vgimport -v -m vgsapp01.map /dev/vgsapp01 /dev/dsk/c7t1d0 /dev/dsk/c7t1d1
Beginning the import process on Volume Group "/dev/vgsapp01".
Physical Volume "/dev/dsk/c7t1d0" contains no LVM information
Physical Volume "/dev/dsk/c7t1d1" contains no LVM information

is it normal ? or how it should be ? I wonder you all can help me. here.

Thank you

[Adisuria Wangsadinata_1]

Hi,

Did you try to run the vgimport for the second time, to find out whether is success or not ?

If it's working, it should be normal since you import the map to the new disks, and on what of the knowledge mine document can be fixed by patch.

Check the url below (docID : 4000089099) about 'HP-UX SCSI: vgimport(1M) for new VolumeGroup fails, then succeeds' :

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000079971639

Hope this information can help you.

Cheers,
AW

[Joseph Loo]

hi,

just like to confirm if the disk are claim:

# ioscan -fnC disk

and also from ioscan output to verify the device name.

regards.

[Adisuria Wangsadinata_1]

Hi,

If your system is Itanium, check the thread below :

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=941133

Hope this information can help you.

Cheers,
AW

[Mark Nieuwboer]

Hi,

Did you do insf -e and then a pvcreate of the disks.
have you done mkdir /dev/vgsapp01
and mknod /dev/vgsapp01/group c 64 (free minor number)
You can check which minor numbers are in use with ll/dev/*/group choose the next free one.
after that you can do the vgimport.

grtz. Mark

[Muda Ikhsan_1]

Hi.. yes i already done pvcreate,and having same minor number.

my system HPUX 11.11

i have 120 lv inside each vg, to create it manually will be a painfull process :)

i tried to activate the vg and it show :
# vgchange -a y /dev/vgsapdbp011
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c7t1d2":
Cross-device link
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c7t1d3":
Cross-device link
vgchange: Warning: couldn't query physical volume "/dev/dsk/c7t1d2":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c7t1d3":

[shridhar_1]

try with -s option

vgexport -v -s -m /tmp/vgXX.map vgXX
vgimport -v -s -m /tmp/vgXX.map vgXX

please tell ur problem in
detail
how u r exporting .....

shri

[Muda Ikhsan_1]

hi i'm exporting using :
#vgexport -v -m -p vgxx.map /dev/vgXX

then try to import it back. i get those error
These are brandnew sets of disks in a new SAN box.

regards..

Thanks :)

[Muda Ikhsan_1]

i try to import using this command :
vgimport -v -m vgsapdbp012.map /dev/vgsapdbp012 /dev/dsk/c7t2d5 /dev/dsk/c7t2d6 /dev/dsk/c7t2d7 /dev/dsk/c7t3d0 /dev/dsk/c7t3d0 /dev/dsk/c7t3d1 /dev/dsk/c7t3d2 /dev/dsk/c7t3d3 /dev/dsk/c7t3d4

[Pete Randall · Accepted solution]

You're trying to use vgimport to do something that it was never intended to do. Read the man page:

"The vgimport command adds the specified volume group to the system. The physical volumes, specified as pv_path ..., are scanned to obtain the volume group information and logical volume information."

The vgimport command is designed to be run against disks that are already defined with LVM information. The most common use is to move disks between servers, vgexporting them from one server and then vgimporting them to another. You can not use vgexport/vgimport to transport LVM definitions from one set of disks to another! To do that, you will have to document your LVM definitions on the original disks and then manually re-create them on the new disks using pvcreate, vgcreate, and lvcreate.


Pete

[Devender Khatana]

Hi,

Pete is right. As you mentioned the disks are new, these can not be configured using vgimport.

If you have one VG configured on one server and want to use same on other server with same disks, vgimport is helpful. For new set of disks you have no other option except creating new VG onto these.

Out of these 120 LUNs you are mentioning, there may be some multiple links to same LUNs, otherwise having such small size of LUN will not benefit much in my opinion.

Creating VG also is not much difficult but plan some parameters properly before creating as you are creating a heavy weight VG.

For this you can also refer to some allready configured similar VG on same or other server.

HTH,
Devender