RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1566677 [details]
originan tmeta of corrupted thinpool

Description of problem:
Thin pool is corrupted and using the upstream tools we couldn't repair it:
thin_repair -i tmeta -o newmeta
thin_dump --repair ...

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Information of the server

sh-4.2# uname -a
Linux opsocss21.consum.red 3.10.0-957.5.1.el7.x86_64 #1 SMP Wed Dec 19 10:46:58 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
sh-4.2# rpm -qa | grep lvm2
lvm2-libs-2.02.180-10.el7_6.2.x86_64
lvm2-2.02.180-10.el7_6.2.x86_64
sh-4.2# thin_repair -V
0.8.0

Created attachment 1567944 [details]
architecture diagram

Created attachment 1568587 [details]
new corrupted metadata from different thinpool

Created attachment 1568588 [details]
Metadata repaired with thin_repair  0.8.1

Can you please try this 1GiB recovery.
(Use 1GiB sized LV for upload of uncompressed metadata)

Created attachment 1568602 [details]
2nd. attached metadata repaired with thin_repair 0.8.1

repaired 1GiB sized version of attachment:
'1568587: new corrupted metadata from different thinpool'

Are the 2 provided metadata files usable ?

Obtained this way:

# create 1G sized empty file
truncate --size 1G  recovery

# repair meta from 512M -> 1G  using version 0.8.1  (currently present in Rawhide)
thin_repair -i  oringal_meta_file -o recovery

This turned out to be https://bugzilla.redhat.com/show_bug.cgi?id=1710533#c54 and not a simultaneous activation issue. The corruption is being handled by RHV through a vdsm hook.

I am closing this bz as it is not a lvm bug causing this corruption.

-Nikhil.