Operating System - HP-UX
1837036 Members
2398 Online
110111 Solutions
New Discussion

vgimport : Couldn't access the list of physical volumes for volume group

 
Lee Herrin
Occasional Contributor

vgimport : Couldn't access the list of physical volumes for volume group

I am trying to install an application on cluster.

I have exported from system A and trying to import in system B using the foll commands:

# vgexport -p -s -m file.out /dev/vgnnm

in system B

vgimport -s -m /etc/cmcluster/nnm/file.out /dev/vgnnm

but i am getting the error message
"Couldn't access the list of physical volumes for volume group "/dev/vgnnm"

something is wrong with this comand or did i miss something ?
5 REPLIES 5
Steven E. Protter
Exalted Contributor

Re: vgimport : Couldn't access the list of physical volumes for volume group

Shalom,

Strings /etc/lvmtab
Check to see that all listed disks for /dev/vgnnnm exist and can be accessed. Use cstm,mstm,or xstm

You may need to rename lvmtab and vgscan -a to get a consistent lvm config.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Rasheed Tamton
Honored Contributor

Re: vgimport : Couldn't access the list of physical volumes for volume group

Is it a DR solution.

Did you create the dir and the group files. Check also the permissions on the dir.

Rgds,
Rasheed Tamton.
Court Campbell
Honored Contributor

Re: vgimport : Couldn't access the list of physical volumes for volume group

Make sure that system B sees the same disks that system A sees. also make sure that the device files for the disks have been created. As mentioned you need to

mkdir dev/vgnnm

and

mknod /dev/vgnnm/group c 64 0xXX0000

on system B. Chage XX in the above example to a hex value that you are not using in another volume group. To get a list of previously used vaules, use:

ll /dev/vg*/group

And that assumes that you named all your vg's beginning with vg in the name. I think you get the picture. Look into that and let us know.
"The difference between me and you? I will read the man page." and "Respect the hat." and "You could just do a search on ITRC, you don't need to start a thread on a topic that's been answered 100 times already." Oh, and "What. no points???"
A. Clay Stephenson
Acclaimed Contributor

Re: vgimport : Couldn't access the list of physical volumes for volume group

The very first thing you should do is an ioscan -C disk -fn to make sure that system B can "see" these devices. Next issue an insf command to create any needed device nodes. When you created the group file on system B for /dev/vgnnn did you make certain that your minor device number is unique on this system?
If it ain't broke, I can fix that.
PC_7
Frequent Advisor

Re: vgimport : Couldn't access the list of physical volumes for volume group

Hi,

Suggesting this:

On System A:

a) # vgexport -v -p -s -m
/dev/

b) rcp or ftp to the same full
path on System B.

On System B :

a) IF same exists, export it out:
# vgexport -v /dev/

b) # mkdir /dev/
c) # mknod /dev//group c 64 0xAB0000
node: replace 0xAB0000 with minor number as on System A (make sure it's unique).

d) # vgimport -v -s -m /dev/

Hope this helps.