Query to VG

[bharat_1]

I trying to create backup recovery tape but received the following error :
Couldn't query VG, Possible error with minor numer.
I have checked for duplication of minor no. but didn't found any. Owner and group of VG00, group file are root:sys
Kindly suggest..

[Michael Tully]

Other than looking for duplicates, perhaps you could also look to see if there are any logical volumes that have a missing minor number. Look at the block and character files.

Also you could look at doing a vgscan of your system.

# cp /etc/lvmtab /et/lvmtab.save
# vgscan

[T G Manikandan]

Got some info from the FAQ

//*
4-5 Why do I get the error: 'The minor number of the volume group exceeds the value Ignite-UX can support.'?

Both make_recovery and make_net_recovery check to ensure that they do not back up a system that Ignite-UX will be unable to recreate.

The A version of Ignite-UX can only create volume groups with group numbers in the range 0 to 10. This is due to the maxvgs kernel tunable being set to 10 in the INSTALL kernel. In order to continue to have Ignite-UX work on systems with 32 MB of memory, the kernel cannot have this parameter increased.

The B version of Ignite-UX does not have this restriction due to reductions in the amount of memory LVM consumes.

It is unusual for the root volume group to have a large volume group number, so it is uncommon to run into this with make_recovery. However, since make_net_recovery can operate on non-root volume groups it is more likely to see the error with that tool.

Workarounds:

If you got into this situation by manually recreating the LVM device files, then consider renumbering them to something less then 10.

If using make_net_recovery, exclude that volume group from the archive.

Use the B version of Ignite-UX which is only officially supported on 11.* releases.
*/

[Sridhar Bhaskarla]

Hi,

Do you see any errors in vgdisplay -v ?. Try

vgdisplay -v > /tmp/vg.out 2>&1

Look at vg.out file. Make sure each volume group that is defined in /etc/lvmtab is existing in /dev/. I remember to see this problem when one of our system administrators deleted /dev/vgxx instead of exporting it.

-Sri

[Ravi_8 · Accepted solution]

Hi,

Looks like corrupted lvmtab

#mv /etc/lvmtba /etc/lvmtab.old
#vgscan
#make_tape_recovery

[RAC_1]

make_tape_recovery/make_recovery -optionsyouwant 2>&1|tee /tmp/recovery.log

check recovery.log for errors.

(this is not same as >2&1 > t.mp/somefile)

[V. V. Ravi Kumar_1]

hi bharat,
iam ravi. i have send a mail to u. pl see that.

1. Check to see if the /dev/slvmvg file exists:

# ll /dev/slvmvg

Note: If the file "does exist", then perform Steps
A, B, C, D, and E.

If the file "does not exist", perform Steps B, C, D,
and E. (do not perform Step A).

2. Perform the following commands:

A. # mv /dev/slvmvg /tmp

B. # mv /etc/lvmtab /etc/lvmtab.currentdate

C. # vgscan -v

D. # strings /etc/lvmtab

Note: This command verifies that everything is correct.

E. # vgdisplay -v /dev/vg00

Note: This command tests the solution.

Best Regards
Ravi