vgimport with a different minor number

[raiden]

guys,

I have recently created a cluster aware VG in a hurry. But later I realised that the minor number which I have used on the primary node is already in use on the secondary node..

Now I want to know than can i vgexport the current vg configuration on a map file, and then vgimport it using a different minor number..

[Ganesan R · Accepted solution]

Hi,

You can. Just export the VG on primary node with map file. Create new minor file and import it.

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

[Steven E. Protter]

Shalom,

Minor number does not effect the ability to do a vgimport.

You have to use mknod to establish this so that you can do the import.

export/import is commonly used to correct errors made in volume group setup, including minor number issues.

http://unix.derkeiler.com/Newsgroups/comp.sys.hp.hpux/2003-10/0365.html

SEP

[Ganesan R]

Hi Raiden,

Typo error in my previous post.

#mknode /dev/vgname/group c 64 0x__0000

should be

#mknod /dev/vgname/group c 64 0x__0000

My sincere apologize for the mistake...

[raiden]

thanks Ganesan and Steven...This clears my doubt