Re: Data recovery -- thin provisioned LVM metadata (?) problem after hardware failure
Zdenek Kabelac <[email protected]>
| Newsgroups | gmane.linux.lvm.devel |
|---|---|
| Message-ID | <[email protected]> |
Dne 03. 05. 23 v 18:48 haaber napsal(a): > Dear Zdenek, > > I had a forced break, but the subject is still active.. > >> >> To get to your thin-pool metadata, you have to activate LV with them. >> (lvchange -ay vgname/thinpoolmetadata). >> > my pool is called qubes_dom0/pool00 (now you know my previous operating > system :) So I tried > > lvchange -ay qubes_dom0/thinpoolmetadata > > but that fails: Failed to find logical volume > "qubes_dom0/thinpoolmetadata" > > Then I tried > > lvchange -ay qubes_dom0/pool00_tmeta Looking at your 'lvs -a' output - you should be able to get this one active. You will need another LV to write fixed metadata into # lvcreate -L128M -n newlv qubes_dom0 Then you run # thin_repair -i /dev/qubes_dom0/pool00_tmeta -o /dev/qubes_dom0/newlv If you get some repaired set which you could probably validate with # thin_dump /dev/qubes_dom0/newlv if you will some some 'good amount' of some data which describe block mapping for many thin volumes. However if you only see couple lines - basically empty thin-pool metadta - you will need to store the content of your original unmodified metadata into a compressed file and upload the file for futher exploration. Let me know what you get from those steps above. Zdenek -- lvm-devel mailing list [email protected] https://listman.redhat.com/mailman/listinfo/lvm-devel