Bug#252164: Package: installation-reports

[Patrick Caulfield <patrick@debian.org>]

On Fri, Jun 11, 2004 at 03:10:18PM +0100, Martin Michlmayr wrote:
> reassign 252164 lvm2
> thanks
> 
> * daveg2@charter.net <daveg2@charter.net> [2004-06-11 06:19]:
> > > In any case, can you type:
> > >   vgchange -a y
> > > and restart the partitioner; then they should show up.
> > > 
> > Done.  For each lv, I get:
> > Incorrect metadata area header checksum
> > Incorrect metadata area header checksum
> > Volume group vg1 metadata is inconsistent
> > Voume group for uuid not found: <about 50 characters> 
> 
> This definitely sounds like an LVM problem then.  Let's ask the LVM
> maintainer for advice.

Ouch, that's  bad error!

Does it only happen with this box or is it more generic? The reason I ask is
because it might be down to O_DIRECT causing odd problems on older hardware - I
have seem this sort of behaviour before and it sort of magically fixed it self
later. If you like I can build you a udeb (or you could do it yourself) with
O_DIRECT disabled to try.

There was an odd bug in earlier lvm2 that used to cause checksum failures but I
can't locate which version that was and I assume that you'll be using a fairly
recent udeb anyway.

One other idea - the disks look quite small, it might be worth using a small PE
size in the vgcreate command. Of course that's only (possibly) helpful in this
case. In the case of a larger disk array, a larger PE size is helpful. 

The effect of PE size on LVM2 is different than it was on LVM1 - it doesn't
restrict the maximum size of an LV but it does seem to impact on the metadata
area sizes. If this turns out to be the problem I'll try to get some metrics
from Alasdair next week. 

-- 

patrick