1833757 Members
2741 Online
110063 Solutions
New Discussion

lvmpvg question

 
sparky_2
Frequent Advisor

lvmpvg question

Hi folks. I am getting the following error message from the vgdisplay command:
"Information from /etc/lvmtab differs from that in /etc/lvmpvg"
The physical volume that is referenced in this file does not actually exist (possibly removed at some point). Is it safe for me to simply remove the lvmpvg file?
6 REPLIES 6
Pete Randall
Outstanding Contributor

Re: lvmpvg question

If you have no PVG(s), then sure, remove it, otherwise just remove the offending entry.


Pete

Pete
Mark Grant
Honored Contributor

Re: lvmpvg question

It is always safe to remove the lvmpvg file but might be irritating if the physical volumes were set up for a good reason.

physical volume groups are often set up so you can guarantee that a logical volume you extend will go over a specified group of disks without all the bother of typing a hundred different disk device file names in your lvextend command.

Personally, I would want to know why the physical volume groups were set up in the first place, it was probably for a good reason.

However, you could just remove the entry for the missing device file from lvmpvg.
Never preceed any demonstration with anything more predictive than "watch this"
hyun-seok kim
Frequent Advisor

Re: lvmpvg question

Hi
first, compare /etc/lvmtab and /etc/lvmpvg
and if it has diffrent device, you can remove it(/etc/lvmpvg)..
UNIX for all
Jakes Louw
Trusted Contributor

Re: lvmpvg question

I hope you haven't removed /etc/lvmpvg. This file is used specifically by LVM for use when determining its strict LVOL assignment, as well as for normal and distributed striping!

Simply edit the file, and remove the line referencing that specific disk.

Trying is the first step to failure - Homer Simpson
sparky_2
Frequent Advisor

Re: lvmpvg question

As it is the only physical volume referenced in the file, I guess I'm safe enough removing it completely, as the info it contains is obsolete....
Cheers
Gerhard Roets
Esteemed Contributor

Re: lvmpvg question

Hi

That file should only be "in use" when logical volumes are modified with the "strict" allocation policy. If lvols get modified when this file is not in place your extend placement could go screwy with regards to your lvol placement scheme.

This would imply then either a loss of redundancy or performance or both.

But as stated above if its part of a legacy configuration flow through and that specific disk assignments is not required anymore it can be turfed.

HTH
Gerhard