This widget could not be displayed.
1845515 Members
2799 Online
110244 Solutions
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
New Discussion
This widget could not be displayed.
This widget could not be displayed.

Error vgimport

 
SOLVED
Go to solution
Eli Daniel
Super Advisor

Error vgimport

SAPL909:/tmp/hp/rfc19032010> vgimport -m ./vgBWaudit.map -s -v vgBWaudit
Beginning the import process on Volume Group "vgBWaudit".
Couldn't access the list of physical volumes for volume group "/dev/vgBWaudit".
SAPL909:/tmp/hp/rfc19032010>
14 REPLIES 14
Eli Daniel
Super Advisor

Re: Error vgimport

Urgent System Producction
James R. Ferguson
Acclaimed Contributor
Solution

Re: Error vgimport

Hi Eli:

Is the import being attempted on a different server than on which the export was done?

Are you sure that all your physical volumes are online/available?

Did you 'vgexport' the volume group with the '-m' and '-s' options?

Regards!

...JRF...
Eli Daniel
Super Advisor

Re: Error vgimport

sapl907 nodo Primary
sapl909 nodo secundary (failover)

sapl907:
mkdir /dev/vgBWaudit
mknod /dev/vgBWaudit/group c 64 0x0b0000
vgexport -m ./vgBWaudit.map -p -s -v vgBWaudit
vgchange -a n vgBWaudit

sapl909:
mkdir /dev/vgBWaudit
mknod /dev/vgBWaudit/group c 64 0x0b0000
vgimport -m ./vgBWaudit.map -s -v vgBwaudit
Beginning the import process on Volume Group "vgBWaudit".
Couldn't access the list of physical volumes for volume group "/dev/vgBWaudit".
James R. Ferguson
Acclaimed Contributor

Re: Error vgimport

Hi Eli:

What OS release is this? Post 'uname -a'.

...JRF...
John Guster
Trusted Contributor

Re: Error vgimport

before import, you need do
ioscan -fn
insf -e

Eli Daniel
Super Advisor

Re: Error vgimport

S.O hp-ux 11.23 Virtual Machine
sapl907(guest) sinfra93(host)
sapl909/guest) sinfra94(host)
James R. Ferguson
Acclaimed Contributor

Re: Error vgimport

Hi (again):

Once again, Are you sure that all your physical volumes are online/available? That is, do you have *device* files shown in an 'ioscan'?

Regards!

...JRF...
Eli Daniel
Super Advisor

Re: Error vgimport

ioscan sapl907 (nodo Primary)

anex
Eli Daniel
Super Advisor

Re: Error vgimport

ioscan sapl909 (nodo secundary failover)
John Guster
Trusted Contributor

Re: Error vgimport

I see what the problem is:
sapl907:
mkdir /dev/vgBWaudit
mknod /dev/vgBWaudit/group c 64 0x0b0000
vgexport -m ./vgBWaudit.map -p -s -v vgBWaudit
vgchange -a n vgBWaudit

on sapl907, there is never a volume group created called vgBWaudit, but you export it. No wonder there is no physical disks accessible becasue this vgBWaudit never associated with any disks.

it should be:
sapl907:
mkdir /dev/vgBWaudit
mknod /dev/vgBWaudit/group c 64 0x0b0000
vgcreate -n vgBWaudit /dev/dsk/cxtxdx
lvcreate -l 100 /dev/vgBWaudit
newfs -F vxfs /dev/vgBWaudit/rlvol1
vgexport -m ./vgBWaudit.map -p -s -v vgBWaudit
vgchange -a n vgBWaudit

Eli Daniel
Super Advisor

Re: Error vgimport

had already been created

vgBWaudit (vg create 18-03-2010)
Chandrahasa s
Valued Contributor

Re: Error vgimport

Hi,
Provide following details:

a)sapl907 and sapl909 your are mentioned, what is purpose of importing vg from sapl907 to sapl909 ?.

b)Provide hpvmstatus -P sapl907 and hpvmstatus -P sapl909 output from vmhost(host where sapl907 and sapl909 lies)

c)Provide ioscan -fnC disk output from vmhost.

d)Provide vgdisplay -v output from sapl907

I can guide you depending on above mentioned output.

shanmuhanandam
HPE Pro

Re: Error vgimport

Hi,
Check the o/p of "strings /etc/lvmtab" for the pv's which are being the part of vgBWaudit VG.Compare the ioscan o/p on node sapl909 node. If the PV's are not availble do the "insf -e -C disk" on the sapl909 node. Now check the ioscan and compare the disks are available. Then try to import the VG.

Thanks,
Shanmugam.
I am an HPE Employee

Accept or Kudo

Eli Daniel
Super Advisor

Re: Error vgimport

thanks,
solution:

nodo secundary
vgimport -c (cluster serviceguard)