Discordance with LVM configuration and Kernel Status

[OLIVA_1]

Hello,

We have lost a disk, so I have removed it from LVM configuration... but it seems I have a discordance between LVM configuration and Kernel status :

vgcfgbackup: /etc/lvmtab is out of date with the running kernel:Kernel indicates 2 disks for "/dev/vgp30arch"; /etc/lvmtab has 1 disks.
Cannot proceed with backup.

Someone can help me to solve this issue ?

Thanks,

[Victor BERRIDGE]

Hi,
I would do an attempt to put /etc/lvmtab fit again:
mv /etc/lvmtab /etc/lvmtab.old
vgscan -va



All the best
Victor

[A. Clay Stephenson]

It appears that you didn't properly "removed it from LVM configuration" (whatever that actually means). A vgscan should bring you back to sanity so : 1) mv /etc/lvmtab /etc/lvmtab.safe 2) vgscan -a

[OLIVA_1]

I have already rebuild /etc/lvmtab with vgscan -va command.
The issue is with Kernel I think, indeed I have 1 disk as LVM configuration indicates not 2 as Kernel thinks...

Thanks,

[Deoncia Grayson_1]

What steps did you take when you removed the other disk? Did you reduced the disk from the volume group? Are you planning to get a new disk?

[Mridul Shrivastava]

Could you please try vgreduce -f

It will remove the disks which are not present in lvmtab.

[A. Clay Stephenson]

But did you rename /etc/lvmtab before doing the vgscan? Also, I assume that /stand/vmunix is the currently executing kernel. For example, if you have built a new kernel and moved it into place but not yet rebooted the the symbol table in /stand/vmunix would not match /dev/kmem and LVM confusion could certainly result.

[OLIVA_1]

My disk was out of order so it wasn't reachable and I have used this command :

vgreduce -l /dev/vg02 /dev/dsk/c7t5d0

after pull out the disk, I am required to do it because the SCSI bus was totally perturbed.

[OLIVA_1]

Yes I have renamed /etc/lvmtab before performing vgscan.

[OLIVA_1]

Yes I have renamed /etc/lvmtab before performing vgscan.
I didn't perform any kernel rebuilt.

[Victor BERRIDGE]

Hi again...
do a :
strings /etc/lvmconf/vgp30arch |more
Do you see the faulty disk here?
If so, I would try to export the vg with a disk definition file something like:
vgexport -v -s -m vgXX.map -f vgXX.pvmap /dev/vgXX
Then edit the pvmap and see the troublesome disk is there, and if so remove it (since no more attached to the system...)
and import again...


Good luck
Victor

[Mridul Shrivastava]

have you tried
vgreduce -f /dev/vg02

whats the outcome of this command.