Dne 09. 04. 26 v 17:55 Ray Davis napsal(a):
Hello,
I’m looking for advice on an LVM-thin metadata corruption case on a Proxmox
host. I have stopped further repair attempts and preserved the current state
for analysis.
Environment
* Proxmox VE host
* Thin pool: `VMDATA0/VMDATA0`
* Backing storage had RAID-5 issues involving two disks
* After reseating the disks, the RAID came back online, but the thin pool
would no longer activate
* Created temporary metadata LVs
* Used `lvconvert --swapmetadata` to extract the pool metadata
* Activated the extracted metadata LV
* Preserved a raw image of the extracted metadata
* Ran `thin_check`
* Ran `thin_repair`
* Ran `thin_dump —repair`
I can provide access to the full case directory or a tarball over HTTP if
someone is willing to look at it. I would prefer to share the link privately
with anyone interested.
My main questions are:
1. Is there any remaining offline recovery path worth trying with the standard
dm-thin/LVM tools?
Hi
Very extensive report - but it looks like the key element here would be -
what are the versions in use.
Kernel ?
lvm2 ?
thin_repair -V ?
2. Does this failure pattern usually indicate that the mapping metadata is
beyond recovery by `thin_repair`/`thin_dump`?
3. Would it be useful to inspect the raw metadata image further, and if so,
what specific tools or commands would you recommend next?
I can provide any command output that would be useful.
If you are using latest tools - then authors of this tool will need to have
access to the damaged metadata whether there is something that can be
recovered.
It'd also greatly help knowing what kind of 'damange' may have caused this.
Regards
Zdenek
