Hello! In case the question comes up: Fedora 28 (the live system I am trying to use for recovery) is using Linux 4.16.3-301.fc28 and `lvm version`: LVM version 2.02.177(2) Library version 1.02.146 Driver version 4.37.0 The system I was originally using to break the cache was using Linux 4.16.7- gentoo, and `LD_LIBRARY_PATH=$PWD/lib64 ./bin/lvm version` from its initrd reports (running on the Fedora 28 live system): LVM version: 2.02.173(2) Library version: 1.02.142 Driver version: 4.37.0 Could someone please give me a hint what is actually broken here? Is it just the metadata? If so, how can that break -- shouldn't that metadata never be modified after creating the LV? And could it not be recovered from /etc/lvm/ archive? What does "manual repair" mean in detail? Is there some way to recover the cache? Or is it at least possible to uncache the LV forcibly, to hopefully recover the data on the origin LV? What is your recommendation to minimise data loss? Best regards, Dennis
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
