Re: [linux-lvm] Incorrect metadata area header checksum

[David Brown <lvm@davidb.org>]

On Sun, Feb 03, 2008 at 07:14:24PM +0100, Eckhard Kosin wrote:

>I just changed the filter rule to
>  
>  filter = [ "r|/dev/cdrom|", "r|^/dev/hda[1,6,7]$|" ]
>
>Now, hda10 will be found, but I get the "Incorrect metadata area header
>checksum" complain from the scanning of hda7:  A citation from the
>output of "vgdisplay -vvv":
>
>...
>        Opened /dev/hda7 RO O_DIRECT
>        /dev/hda7: block size is 1024 bytes
>      /dev/hda7: lvm2 label detected
>        Closed /dev/hda7
>        lvmcache: /dev/hda7 now orphaned
>        Opened /dev/hda7 RO O_DIRECT
>        /dev/hda7: block size is 1024 bytes
>  Incorrect metadata area header checksum
>        Closed /dev/hda7
>        Opened /dev/vg_uhu00/var_cache_rsnapshot RO O_DIRECT

Ok, the problem here isn't that you should have to create filter rules to
eliminate these volumes, but that it thinks it is finding an lvm2 label on
the volume.

I'm going to guess that at some point, these partitions had an LVM label on
them, and then a regular filesystem was placed on them.  Several
filesystems don't overwrite the first 1k or so of the volume, so the label
isn't going to be obliterated, just corrupted.

Can you do something like:

   dd if=/dev/hda7 bs=1k count=1 | hexdump -C

You'll probably find that there is a lvm2 label there.  I'm not sure of a
safe way of elminiating it.

David