topic Re: vgimport error: Unable to read the physical volume in Operating System - HP-UX

vgimport error: Unable to read the physical volume

WSS — Tue, 07 Feb 2006 09:24:04 GMT

Hi All,

Looked at some of the foum responses, but nothing seems to answer my error directly. I don't think the physical paths have changed at all, and I get this error when trying to import the map file from the primary node to the secondary node.

Unable to read the physical volume

I have just added another mount point and logical volume to a package, and trying to map the volume group on the secondary node. These are the steps I used for the vgexport and vgimport -

On Primary Node -

# vgexport -v -p -m /tmp/vgclwss.map
/dev/vgclwss
Beginning the export process on Volume Group "/dev/vgclwss".
vgexport: Volume group "/dev/vgclwss" is still active.
/dev/dsk/c4t0d3
/dev/dsk/c4t0d4
/dev/dsk/c4t0d5
/dev/dsk/c4t0d6

root@ugos388# rcp /tmp/vgclwss.map ugos389:/tmp/

Doing the vgexport on secondary node and vgimport

root@ugos389# vgexport /dev/vgclwss
Physical volume "/dev/dsk/c4t0d3" has been successfully deleted from
physical volume group "PV0".
Physical volume "/dev/dsk/c4t0d4" has been successfully deleted from
physical volume group "PV0".
Physical volume "/dev/dsk/c4t0d5" has been successfully deleted from
physical volume group "PV0".
Physical volume "/dev/dsk/c4t0d6" has been successfully deleted from
physical volume group "PV0".
root@ugos389# mkdir /dev/vgclwss
root@ugos389# mknod /dev/vgclwss/group c 64 0x030000
root@ugos389# vgimport -v -m /tmp/vgclwss.map /dev/vgclwss
Beginning the import process on Volume Group "/dev/vgclwss".
vgimport: Unable to read the physical volume.root@ugos389#

Does anyone have any ideas??
Thanks in advance

Re: vgimport error: Unable to read the physical volume

Sundar_7 — Tue, 07 Feb 2006 09:27:56 GMT

You should use -s option with vgexport. Otherwise you will need to specify the PV device files with vgimport.

From the primary node

# vgexport -p -v -s -m vg.map /dev/vg

# rcp -p vg.map secondarynode:/tmp

In the secondary node

# vgexport ..
# mkdir /dev/vgname
# mknod /dev/vgname/group c 64 0xYY0000
# vgimport -s -v -m /tmp/vg.map /dev/vgname

Re: vgimport error: Unable to read the physical volume

James R. Ferguson — Tue, 07 Feb 2006 09:35:55 GMT

Hi:

You need to either specify the physical paths during the 'vgimport' or specify '-s' during the 'vgexport' and 'vgimport'. Using '-s' collects the VGID into the mapfile and allows matching physical disks by that VGID in lieu of the path.

Regards!

...JRF...

Re: vgimport error: Unable to read the physical volume

Bharat Katkar — Tue, 07 Feb 2006 09:36:06 GMT

Yes "-s" needs to be specified while you export and import the shared VG.

Extract from Man Page of vgexport:
"Sharable option, Series 800 only. When the -s option is specified, then the -p, -v, and -m options must also be specified.
A mapfile is created that can be used to create volume group entries on other systems in the high availability cluster (with the vgimport command)."

Hope that helps.
Regards,

Re: vgimport error: Unable to read the physical volume

WSS — Tue, 07 Feb 2006 09:38:11 GMT

Yes I read the -s option in the man pages, but what does "Series 800 only" mean???

I will try the vgexport with the -s and then try the vgimport again and let you all know. Thanks alot

Re: vgimport error: Unable to read the physical volume

Bharat Katkar — Tue, 07 Feb 2006 09:42:14 GMT

Series 800 only means only for Server Class.

Series 700 is for workstations.

These are the only two series that exists now.

Regards,

Re: vgimport error: Unable to read the physical volume

WSS — Tue, 07 Feb 2006 09:52:59 GMT

Problem fixed :-)
Thanks for all your replies, the -s option fixed it. Have assigned points....
Regards
Trev

Re: vgimport error: Unable to read the physical volume

WSS — Tue, 07 Feb 2006 09:55:45 GMT

The -s option as advised fixed my problem. Thanks alot