Group file Invalid minor number

[Mitchell Gaddy]

I come across a VG that has a invalid minor number "0x07e100". I want to correct the problem when I migrate the data onto a new server. I tried a vgexport/vgimport and create a new group file with a new minor number but it will not import the data and still reports the error. Is there anyway to create a new group file for an existing VG.

[Pete Randall]

That's exactly the approach I would try. What error are you getting when you try to import the data?


Pete

[John Poff]

Hi,

I would expect a minor number of something like:

0x070000

I'm not sure where your 'e100' came from but that doesn't look right.

JP

[Geoff Wild]

Interesting - how did the minor number get corrupted?

What is the date of the file compared to others in that dir?

Is this vg07?

Minor number should be 0x070000

Rgds...Geoff

[A. Clay Stephenson]

The group file should be major devic3 64 and minor device 0x070000. Do an ls -l /dev/vg*/group and make certain that minor device number is unique.

[Geoff Wild]

Got a good backup?

Is it already vgexported?

Were you able to get a map file:

vgexport -s -v -p -m /tmp/vg07.map /dev/vg07

How are you importing?

Did you:

mkdir /dev/vg07
mknod /dev/vg07/group c 64 0x070000

vgimport -s -v -m /tmp/vg07.map /dev/vg07

And are there no other minor numbers the same?

ll /dev/vg*/group

Rgds...Geoff

[Mitchell Gaddy]

Whoever created this VG gave it the minor number "0x07e100". I'm trying to change it to "0x070000" but it will not allow. When I try to import the mapfile over onto the new server it still trying to reference the old minor number. I think because the disk associated with the VG the headers are mark with the VG minor number that it was assigned when created. I can still examine the VG and make LV's but I just get that error message "Invalid Minor number" before it displays the VG information from the vgdisplay command. I wanted to take this time to clean up everything since its being moved.

[Geoff Wild]

Does every lvol have that "corrupt" minor number as well - or jsut the group file?

Rgds...Geoff

[Mitchell Gaddy]

no all the other LV'S have a minor number of 0x07001-7. Just the group file has a minor number of 0x07e100. I also tried to create a new group file on the original server but the after doing the and running the vgdisplay command it could not display the VG so I had to move the old group file back.

[A. Clay Stephenson]

This makes no sense. The group minor device number is not recorded in the LVM reserved areas although the VGID is. If what you are saying is true, one could not, for example, convert vg02 into vg10 via vgexport/vgimport but that process is done everyday. You seem to be trying a vgexport/vgimport using the -s option. I would bypass that step and explicitly list the PV's; the mapfile then would only record the LVOL names and wouldn't even be needed if the standard lvol1, lvol2, ... convention is used. Man 7 LVM; it explains the composition of the group file device node and yours is bogus. I do assume that you are up to date on LVM patches.

[AshishJain_USA]

Hi

1. Pls create the map file without -s option of vgexport.
2. Make sure to note down the disks device files within this Volume group.
3. Export the VG
4. You may now follow the simple steps of importing a voulme group using the new map file and specifying the disks.

rgds...Ashish

[Geoff Wild]

I wonder, if just re-creating the group file would work?

Backup the /dev.vg07 dir (just tar it) - then remove the group file and run the mknod command...

Rgds...Geoff

[A. Clay Stephenson]

I assume that when you did the vgexport, it blew away the group device node and the associated LVOL device nodes as well as the /dev/vgxx directory itself. That is the normal behavior of vgexport w/o the -p option.

[Senthil Kumar .A_1]

Hi Mitchell,

Whats the latest update regards to this issue,

Let us know, so that we could suggest further based on ur reply to get you through with this issue.

Regards,
Senthil Kumar .A