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:
The command line in v0.6.x has changed slightly.  If you want to specify the block for the metadata snap you should now use --metadata-snap=<sb>.  -m  should be used on it's own (the tools will look up the metadata snap location themselves).

Although, according to thin_dump man "-m" and "--metadata-snap" are the same. Could the man page be updated in this BZ?

       -m, --metadata-snap [block#]
       Dump metadata snapshot created by device-mapper thin provisioning target.  If block is not provided, access the default metadata snapshot created by the thin provisioning device-map-
       per target, else try the one at block#.  See the thin provisioning target documentation on how to create or relea

Version-Release number of selected component (if applicable):
device-mapper-persistent-data-0.6.2-0.1.rc5.el6

How reproducible:
100%

Steps to Reproduce:
1.man thin_dump

https://github.com/jthornber/thin-provisioning-tools/commit/5bac06d68fec021c736a0c86af3fa9507d0df9aa

 device-mapper-persistent-data-0.6.2-0.2.rc7.el6:
       -m, --metadata-snap[=block#]
       Dump metadata snapshot created by device-mapper thin provisioning target.  If block  is not  provided,  access  the  default metadata snapshot created by the thin provisioning device-mapper target, else try the one at block#.  See  the  thin  provisioning  target documentation  on  how  to create or release a metadata snapshot and retrieve the block number from the kernel.

# thin_dump /dev/sda -m=1
couldn't parse <metadata_snap>
--snip--
# thin_dump /dev/sda --metadata-snap=1
bad checksum in superblock

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1913