Re: Data recovery -- thin provisioned LVM metadata (?) problem after hardware failure

Hi Ming

thank you so much. I compiled it, and did make install, but lvconvert is
still the old one. It should be possible to do the job with  
pdata_tools  directly, right !?  I had formerly created a
"newlv" inside my qubes_dom0 pool, so I did   run

./pdata_tools  thin_repair -i /dev/qubes_dom0/pool00_tmeta   -o
/dev/qubes_dom0/newlv

that command worked 5 seconds, and came back without any notice, which
usually is good sign. I did not run it with a verbose flag, stupid me.

Can I now run some command that activates the pool with "newlv" as
metadata ? Or backup the old metadata file, and then copy "newlv"
metadata into the pool00_tmeta ? I am, of course,  afraid of destroying
it all, so close to  the end, so I better ask once more  :-)

best, Bernhard




On 5/17/23 17:17, Ming Hung Tsai wrote:
> Hi,
>
> I've pushed the changes upstream. Now you should be able to repair the
> pool via "lvconvert --repair" after installation.
>
> On Thu, May 11, 2023 at 3:39 PM haaber <[email protected]> wrote:
>
>     Dear all,
>
>     We need the exact binary copy of _tmeta  LV  - thus just use
>     >
>     > dd if=/dev/qubes_dom0/pool00_tmeta  /tmp/tmeta_copy bs=512K
>     > bzip2 /tmp/tmeta_copy
>     >
>     the output is here: https://we.tl/t-AEmlc5CYeH
>
>     > With this data - also provide full lvm2 metadata for this VG
>     > (should be as a file in  /etc/lvm/backup  - or you could run
>     > just vgcfgbackup)
>     >
>     I attached that one directly. Thank you very much!
>
>     best, Bernhard
>
>
> --
> lvm-devel mailing list
> [email protected]
> https://listman.redhat.com/mailman/listinfo/lvm-devel

--
lvm-devel mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/lvm-devel