vgimport problem

[khilari]

Hi people, okay this is the scenerio.
On server1:
# strings /etc/lvmtab
/dev/vg00
/dev/dsk/c0t6d0
/dev/vg01
/dev/dsk/c6t0d1
/dev/vg03
/dev/dsk/c3t6d0

Now, i am using /dev/vg03 as the shared volume and the disk is c3t6d0.

I made a /tmp/mcsg.map file and both nodes have it, with the same VGID.
# cat /tmp/vgmcsg.map
VGID 920bc9324422efd5
1 mcsg

Now when i try to vgimport i am getting the error.

# vgimport -svp -m /tmp/vgmcsg.map /dev/vg03
Beginning the import process on Volume Group "/dev/vg03".
Couldn't access the list of physical volumes for volume group "/dev/vg03"

U can see in the /etc/lvmtab that the entry for c3t6d0 is under vg03, and i had a successful vgexport:
# vgexport -svp -m /.mp/vgmcsg.map /dev/vg03
Beginning the export process on Volume Group "/dev/vg03".
/dev/dsk/c3t6d0

Now, on the other server i did vgimport an di am getting:

# vgimport -svp -m /tmp/vgmcsg.map /dev/vg03
Beginning the import process on Volume Group "/dev/vg03".
Couldn't access the list of physical volumes for volume group "/dev/vg03".

And i wonder y?
Thanks.

[A. Clay Stephenson]

Is this a fibre/SAN connected disk? If so does server2 have access to it. Have you done an ioscan -fn and insf on server2 since attaching the disk?

A posting of ioscan -C disk -fn on both boxes would be helpful.

[Patrice Le Guyader]

Hello,


Try to make a ioscan -fnC disk and after an insf. It should be better after.

Regards
Pat

[Ninad_1]

Khilari,

I can think of 2 possible reasons -
1) As ponited out by Clay and Patrice either the disks are not visible to your 2nd server, so 1st check if the disks are visible to 2nd server
2) The physical volume name for
any given disk may be different on one node than it is on another. If this is the case you may need to modify the copied vgmcsg.map file to reflect the changes before importing the volume groups.

Regards,
Ninad

[Bharat Katkar]

Hi,
I doubt mostly about the second point that ninad has pointed out.
If that is the case then specifying the correct PV name with vgimport command would be the solution.
Regards,

[Devender Khatana]

Hi,

Using -s option at the vgexport will add VGID in the mapfile and same will be matched with available disks on the system where vgimport is executed. So this only lefts one option as indicated earlier by others i.e. the disk is not accessible to the host.

HTH,
Devender

[Chan 007]

Hi,

Trying giving the diskinfo /dev/rds/cXtYdZ,

if your out put shows the disk then you would be able to create the VG.

Also As pointed by Ninad, your PV is incorrect. So check once again.

Chan

[Chan 007]

Hi,

Trying giving the diskinfo /dev/rdsk/cXtYdZ,

if your out put shows the disk then you would be able to create the VG.

Also As pointed by Ninad, your PV is incorrect. So check once again.

Chan

[khilari]

i couldnt post my outputs here, kindly check another thread in hp admin, continuing this one.