vgimport fails.

[fizan]

srvr A:
# vgexport -s -v -m /etc/lvmconf/vg01.map vg01
Beginning the export process on Volume Group "vg01".
/dev/dsk/c3t2d0
vgexport: Volume group "vg01" has been successfully removed.

srvr B :
# vgimport -s -v -m /etc/lvmconf/vg01.map vg01 /dev/dsk/c3t2d0
Beginning the import process on Volume Group "vg01".
Couldn't access the list of physical volumes for volume group "/dev/vg01".

in srvr B: o/p of strings /etc/lvmtab:
# strings /etc/lvmtab
/dev/vg00
/dev/disk/disk36_p2
import is not performing plz help me out..

Thanks.

[Lijeesh N G_1]

Hi,

Make sure the disk is accessible from both the nodes,

Provide following command outputs from both servers,

#ioscan -fnC disk
#strings /etc/lvmtab

Another thing if you mentioning -s switch, no need mention disk device file again,
just # vgimport -s -v -m /etc/lvmconf/vg01.map vg01 is enough.

Regards,
LIJEESH N G

Regards,
LIJEESH N G

[fizan]

# vgimport -s -v -m /etc/lvmconf/vg01.map vg01
Beginning the import process on Volume Group "vg01".
Couldn't access the list of physical volumes for volume group "/dev/vg01".
-------------------------------------------
srvr A:

# strings /etc/lvmtab
/dev/vg00
/dev/disk/disk36_p2
bcoz /dev/vg01 is removed wen i give vgexport before tat vg01 is present.
# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 3 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 0 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
/dev/dsk/c2t1d0s1 /dev/rdsk/c2t1d0s1
/dev/dsk/c2t1d0s2 /dev/rdsk/c2t1d0s2
/dev/dsk/c2t1d0s3 /dev/rdsk/c2t1d0s3
disk 2 0/1/1/1.2.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk 16 0/4/1/0.102.13.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
disk 17 0/4/1/0.102.13.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d2 /dev/rdsk/c11t0d2
disk 18 0/4/1/0.102.13.0.0.0.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d3 /dev/rdsk/c11t0d3
disk 19 0/4/1/0.102.13.0.0.0.4 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d4 /dev/rdsk/c11t0d4
disk 8 0/4/1/0.102.14.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c7t0d1 /dev/rdsk/c7t0d1

[fizan]

just help me with steps involved in vgexport and vgimport in two servers A and B?

[Mel Burslan]

In your srvrB ioscan output, disk identified by c3t2d0 looks like it is a local drive. How can a local drive have the same vgid information with another drive on another server ?

vgimport basically reads the LVM header blocks on the given disk and match those with the map file you provide on the command line to reconstruct (a.k.a. import) the LVM structure.

I am not quite sure what exactly you are trying to do here. Please provide output from

ioscan -fnC disk

srvr A for better understanding.

[fizan]

# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 3 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 0 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
/dev/dsk/c2t1d0s1 /dev/rdsk/c2t1d0s1
/dev/dsk/c2t1d0s2 /dev/rdsk/c2t1d0s2
/dev/dsk/c2t1d0s3 /dev/rdsk/c2t1d0s3
disk 2 0/1/1/1.2.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk 16 0/4/1/0.102.13.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
disk 17 0/4/1/0.102.13.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d2 /dev/rdsk/c11t0d2
disk 18 0/4/1/0.102.13.0.0.0.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d3 /dev/rdsk/c11t0d3
disk 19 0/4/1/0.102.13.0.0.0.4 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d4 /dev/rdsk/c11t0d4
disk 8 0/4/1/0.102.14.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c7t0d1 /dev/rdsk/c7t0d1
disk 9 0/4/1/0.102.14.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c7t0d2 /dev/rdsk/c7t0d2
disk 10 0/4/1/0.102.14.0.0.0.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c7t0d3 /dev/rdsk/c7t0d3
disk 11 0/4/1/0.102.14.0.0.0.4 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c7t0d4 /dev/rdsk/c7t0d4
disk 4 0/4/1/0.109.13.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c5t0d1 /dev/rdsk/c5t0d1
disk 5 0/4/1/0.109.13.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c5t0d2 /dev/rdsk/c5t0d2
disk 6 0/4/1/0.109.13.0.0.0.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c5t0d3 /dev/rdsk/c5t0d3
disk 7 0/4/1/0.109.13.0.0.0.4 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c5t0d4 /dev/rdsk/c5t0d4
disk 12 0/4/1/0.109.14.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t0d1 /dev/rdsk/c9t0d1
disk 13 0/4/1/0.109.14.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t0d2 /dev/rdsk/c9t0d2
disk 14 0/4/1/0.109.14.0.0.0.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t0d3 /dev/rdsk/c9t0[rx26-207]/dev

[Vishu]

Hi fizan,

I agree with Mel on this. your disk c3t2d0 looks like a local disk to the server. the option -s with vgimport scans for LVM header for the same VG ID information, which it has in its map file. Mostly used in shared storage or while moving disks from one server to other.

Now, if you want to import it on other disk, then avoid using the -s option and import it by specifying the disk name.

[Prashanth Waugh]

Hi Fizan,

the syntax should be like that
on

srvr A:
vgexport -v -s -p -m /tmp/vgu1.map /dev/vgu1

on server B:
vgexport -v -s -m /tmp/vgu1.map /dev/vgu1

Pls check the man pages for vgexport and vgimport

Regards,
prashant

[fizan]

if i export in server A it results as vg01 is removed?

normally vgexport removes thy exporting vg?

[Patrick Wallek]

>>if i export in server A it results as vg01 is removed?

Yes!

>>normally vgexport removes thy exporting vg?

Yes, unless you add the '-p' (preview) option to the vgexport command.