1833780 Members
2367 Online
110063 Solutions
New Discussion

minor number conflict

 
SOLVED
Go to solution
srinimar
Frequent Advisor

minor number conflict

i have exported a VG. to other node. i am trying to import it but igot this error. but i have set the same minor and major number as we have it on the other node.

vgimport: Minor number of /dev/vgora/group is not unique. /dev/finvol/group has
the same minor number.

we have /dev/finvol on node B.
13 REPLIES 13
IT_2007
Honored Contributor

Re: minor number conflict

you don't have to match same minor number for the hosts. It should be unique. cleanit up and create again.

mkdir /dev/vgXX
mknod /dev/vgXX/group c 64 0xAA0000
then
vgimport ......
A. Clay Stephenson
Acclaimed Contributor

Re: minor number conflict

The error message says it all.

Do an ls -l /dev/vg*/group and compare the minor device numbers on the group files. The minor device number must be unique on a given host. You need to rm /dev/vgora/group and recreate the device node. It is not required that the same minor device numbers be used on all the nodes in the cluster just that the name of the VG be the same.
If it ain't broke, I can fix that.
Pete Randall
Outstanding Contributor

Re: minor number conflict

If you need /dev/vgora/group to have the same minor number as it has on node B, then you will have to change the minor number for /dev/finvol/group. You should be able to export it, re-create the group file with a unique minor number, and then re-import it.


Pete

Pete
srinimar
Frequent Advisor

Re: minor number conflict

now i got the below message...on node B.


# vgimport -s -m /tmp/vgora.map /dev/vgora
vgimport: Cannot open the control file "/dev/vgora/group":
No such device


A. Clay Stephenson
Acclaimed Contributor

Re: minor number conflict

Did you create your /dev/vgora/group file before trying to vgimport? This file (and its parent directory) must exist prior to executing vgimport.
If it ain't broke, I can fix that.
srinimar
Frequent Advisor

Re: minor number conflict

yes i have done that on node B.

# pwd
/dev/vgora
# ls -l
total 0
crw-rw-rw- 1 root sys 64 0xaa0000 Sep 14 12:17 group
#

Pete Randall
Outstanding Contributor

Re: minor number conflict

I think you have a problem with your minor number. You have 0xaa0000. The minor number needs to be less than the kernel parameter "maxvgs" and aa (170) is a bit higher, I expect. Try 0x0a0000.


Pete

Pete
srinimar
Frequent Advisor

Re: minor number conflict

i have changed it to 64 0x0a0000 still i go this error

# vgimport -s -m /tmp/vgora.map /dev/vgora
vgimport: Cannot open the control file "/dev/vgora/group":
No such device

i have this setting on the node A 64 0x010000

and my maxvgs -10 (max)
srinimar
Frequent Advisor

Re: minor number conflict

i have this two minor numbers i have for other volumes on the same node


64 0x010000
64 0x000000
Patrick Wallek
Honored Contributor
Solution

Re: minor number conflict

If maxvgs is 10, then you minor number needs to be in the range 0x000000 thru 0x090000.

0x0a0000 would be the 11th VG.
A. Clay Stephenson
Acclaimed Contributor

Re: minor number conflict

Normally one of the first things that you do for any host that is going to be part of an MC/SG cluster is to increase maxvgs up to at least something near 32 to avoid just your kinds of problems.
If it ain't broke, I can fix that.
srinimar
Frequent Advisor

Re: minor number conflict

Thnx all of them I am done with it.
srinimar
Frequent Advisor

Re: minor number conflict

I have found the reply and it solved my problem.