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.

Description of problem:
thin_check manpage issue:
there is an example in thin_check.
====
     thin_check /dev/vg/metadata
====

it's better to change the device to /dev/mapper/vg-pool_tmeta since the internal thin meta device is not accessed in /dev/vg/.

same issues for thin_dump & thin_restore.


Version-Release number of selected component (if applicable):
device-mapper-persistent-data-0.1.4-2.el7.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

It's only as an example.

Current version of (2.02.98-5) lvm2 allows you to i.e. 'export/swap' metadata from thin pool to a normal LV - and you could use then  thin_check on a normal LV - fix metadata/ backup&restore them to bigger partition.

So I think the man page could be left as it is.

User should never try to fix/run  think_check on 'running'  thin pool.
The only exception currently is, when thin pool fails to start -
we leave the thin metadata device active - but it's rather 'temporary'
solution - and at this moment we should probably already disable this use,
since there is a way, to fix thin pool without this.

Obviously we are missing proper documentation how to fix thin pool metadata
with current lvm2 utilities, which needs to be written.

BZ#1022850 is a separate BZ for documenting fixing thin pool metadata with current lvm2 utilities.

There is now an lvmthin(7) man page which may address this issue.