Operating System - HP-UX
1834150 Members
3584 Online
110064 Solutions
New Discussion

Re: Problems with vgimport

 
SOLVED
Go to solution
Carles Viaplana
Valued Contributor

Problems with vgimport

I added new LV lvol12 to VG vgspe0 on a cluster's node1 but when I imported configuration to node2 it failed:

# vgimport -vs -m /etc/lvmconf/vgspe0.mapfile /dev/vgspe0
Beginning the import process on Volume Group "/dev/vgspe0".
vgimport: Volume group "/dev/vgspe0" already exists in the "/etc/lvmtab" file.
#

I know vgspe0 already exists on node2 but LV lvol12 doesn't exist.

Do you have any idea what happens?

Thanks!
6 REPLIES 6
Denver Osborn
Honored Contributor
Solution

Re: Problems with vgimport

you can use mknod to create the dev file for the new lvol.

on active node "ll /dev/spe0/lvol12" to get the minor #.

on passize node "mknod /dev/spe0/lvol2 b 64 0xNNNNNN" and "mknod /dev/spe0/rlvol2 c 64 0xNNNNNN"

where 0xNNNNNN is the minor number you get from "ll" on active node.

Then if make sure if you updated the package script on the active node that those changes also get pushed out to the passive node.

If you want to vgimport vs. using mknod, you'll have to vgexport that VG from node2 1st. mknod would be easier and get the same results.

Hope this helps,
-denver
Alan Meyer_4
Respected Contributor

Re: Problems with vgimport

yes, the VG already exists on node2 but it is not current, so what you need to do is to remove the VG from node2 and then re-do the vgimport on node2.

** Make sure that it is a newly exported map file from node1.
" I may not be certified, but I am certifiable... "
Victor Fridyev
Honored Contributor

Re: Problems with vgimport

Hi,

You have to remove the updated vg from the
second node with
ls -ls /dev/vgspe0/group
vgexport vgspe0
And import it with:
mkdir /dev/vgspe0
mknod /dev/vgspe0/group c 64 0xNNNNNN
vgimport /dev/vgspe0 /dev/dsk/XXXXXX

Use the hexa number from the output of ls

HTH
Entities are not to be multiplied beyond necessity - RTFM
Geoff Wild
Honored Contributor

Re: Problems with vgimport

On first node, create a map file:
vgexport -s -p -v -m /tmp/vgspe0.map /dev/vgspe0
rcp /tmp/vgspe0.map node2:/tmp/vgspe0.map

On second node, vgexport /dev/vgspe0
mkdir /dev/vgspe0
mknod /dev/vgspe0/group c 64 0xHH0000
(where HH is the hex minor number)
vgimport -s -v -m /tmp/vgspe0.map /dev/vgspe0

Rgds...Geoff



Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Geoff Wild
Honored Contributor

Re: Problems with vgimport

Meant to add that the following is a good doc to read:

http://docs.hp.com/en/B3936-90079/index.html

In particular - chapter 5:

http://docs.hp.com/en/B3936-90079/ch05s04.html#d0e10936

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Carles Viaplana
Valued Contributor

Re: Problems with vgimport

Thanks to all for your replies!

This document explains how to do it:

http://docs.hp.com/en/B3936-90079/ch05s04.html#d0e10936