Problem with vgimport

[Wilder Mellotto]

Hi.

I have a 2 node cluster, and I need a VG to be added.

I created the VG in the first node without problem. Then:

vgexport -p -m vgoraarch01.map vgoraarch01

In the second node, when I tried to impor, i have the annoying message:

root@brcsfpbd01:/tmp >vgimport -v -m vgoraarch01.map -f disk.infile vgoraarch01
Beginning the import process on Volume Group "vgoraarch01".
vgimport: Minor number of /dev/vgoraarch01/group is not unique. /dev/vgoraarch01/group has the same minor number.

Then Iroot@brcsfpbd01:/tmp >vgimport -v -m vgoraarch01.map -f disk.infile vgoraarch01
Beginning the import process on Volume Group "vgoraarch01".
vgimport: Minor number of /dev/vgoraarch01/group is not unique. /dev/vgoraarch01/group has the same minor number.

With vgscan -p, please check the attached file. I can not create any other VG, with any other minor. I tested a lot of minor numer, from oe to 5e, but I cant make it.

Please, help me.

[Duncan Edmonstone]

Just a guess, but check the value of kernel parameter maxvgs.

on 11.11:

kmtune -q maxvgs

on 11.23:

kctune -q maxvgs


Obviously you need it to be higher than the number of VGs you have.

HTH

Duncan

[Ramesh S]

Hi

>>Make sure that you have unique same minor numbers for all shared volume groups across the nodes in cluster.

>>I would always create map file with "-s" option to get VGID on map file.

#vgexport -p -v -s -m

[Sp4admin]

Hello,

It sound like the minor number is incorrect.

To change the minor numbers we did:
unmount the filesystem
vgchange -a n /dev/vgXX
vgexport -v -s -m vgXX.map /dev/vgXX
mkdir /dev/vgXX
chmod as necessary for /dev/vgXX
mknod /dev/vgXX/group c 64 0xwhatever-it-should-be
vgimport
vgchange -c y /dev/vgXX
vgchange -a e /dev/vgXX
mount the filesystem

Hope this helps!
sp,

[Mounaam · Accepted solution]

Hi,

1st/ search if you have a large file (>2Go) on /dev

2nd/ what is your LVM patch level?
PHCO_33310 fix this defect for 11.11:
( SR:8606410321 CR:JAGaf70203 )
On a system installed with PHCO_24809 or any of its
superseding patches, and when files with sizes larger than
MAX_SMALL_FILE (2147483647) exist under the /dev directory,
vgcreate(1M), vgimport(1M) and vgscan(1M) might fail with
error messages as shown below.
vgcreate(1M) and vgimport(1M) logs message similar to:
"Minor number of /dev/xxx/xxx is not unique. /dev/xxx/xxx
has the same minor number".
and vgscan(1M) logs messages similar to:
"Error getting path name of volume group with group file
minor number 0x0.
Value too large to be stored in data type".
On 11.23 it's corrected by PHCO_34421.

[Ramesh S]

Hi

Yes, Duncan is correct. It could be a issue with maxvgs. Defaukt value is 10. Check that , if you have 10 vg's already, you may need to increase that value and reboot that node.

Good things is .. In 11iv3, maxvgs kernel parameter is been removed.

Best Regards,
Ramesh

[Wilder Mellotto]

Its not a problem with nimor number. ALL my minor number seems to be in use, please read my attached file in first post.

kmtune -q maxvgs
Tunable Value Expression
maxvgs 100 100

PHCO_35063 1.0 LVM commands patch

[Ramesh S]

Hi

For 11iv2, Latest LVM commad patch is PHCO_36744 and it fixes this issue.


( SR:8606399189 CR:JAGaf59154 )
When files of size greater than MAX_SMALL_FILE (2147483647
bytes) exist under the /dev directory,
vgcreate(1M) and vgimport(1M) throw error messages similar
to:
"Minor number of /dev/dsk/file1 is not unique.
/dev/dsk/file2 has the same minor number".

vgscan(1M) throws messages similar to:
"Error getting path name of volume group with
group file minor number 0x0.Value too large to be stored
in data type".

Best Regards,
Ramesh

[Jeeshan]

Hi Wilder

post your ll /dev/*/group output of every node.

[Wilder Mellotto]

Thanks a lot Ramesh PHCO_36744 resolved my problem.

After the reboot, I imported the VG using my minor number 0x0e without problem.

Thanks again.