On Mon, Jun 10, 2019 at 10:59:43PM +0300, Nir Soffer wrote: > > [root@uk1-ion-ovm-18 pvscan > > /dev/mapper/36000d310056978000000000000000014: Checksum error at offset > > 4397954425856 > > Couldn't read volume group metadata from > > /dev/mapper/36000d310056978000000000000000014. > > Metadata location on /dev/mapper/36000d310056978000000000000000014 at > > 4397954425856 has invalid summary for VG. > > Failed to read metadata summary from > > /dev/mapper/36000d310056978000000000000000014 > > Failed to scan VG from /dev/mapper/36000d310056978000000000000000014 > > This looks like corrupted vg metadata.
Yes, the second metadata area, at the end of the device is corrupted; the first metadata area is probably ok. That version of lvm is not able to continue by just using the one good copy. Last week I pushed out major changes to LVM upstream to be able to handle and repair most of these cases. So, one option is to build lvm from the upstream master branch, and check if that can read and repair this metadata. > David, we keep 2 metadata copies on the first PV. Can we use one of the > copies on the PV to restore the metadata to the least good state? pvcreate with --restorefile and --uuid, and with the right backup metadata could probably correct things, but experiment with some temporary PVs first. _______________________________________________ Users mailing list -- email@example.com To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://firstname.lastname@example.org/message/6T7EM2R7422CXGBO3CKALMIHBYSTBUYK/