Comment # 9 on bug 926405 from Lidong Zhong

(In reply to lynda t from comment #8)
> (In reply to Lidong Zhong from comment #7)
> > Thank you. I think we got the reason now. There is indeed an data overflow.
> > We will make a upgrade later.
> > 
> > Could you use the default pvmetadatacopies value as a workaround? After the
> > upgrade, you can change your vg back.
> 
> I don't think so.
> 
> Can that be done for an *existing* PV that already has a VG with LVs on it?
> 
> IIUC it's not possible to change the PV metadata/data-alignment once it's
> been created.  I'd have to destroy then recreate the PV/VG/LVs.
> 
> Correct?
> 
I am afraid you are right. Implementing vgchange --metadatacopies 2
volgroupname seems couldn't make the single pv store 2 copies of the metadata.
Thanks.

> LT