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:

[root@qalvm-01 ~]# vgcfgrestore snapper_thinp
  Consider using option --force to restore Volume Group snapper_thinp with thin volumes.
  Restore failed.

[root@qalvm-01 ~]# vgcfgrestore --force snapper_thinp
  WARNING: Forced restore of Volume Group snapper_thinp with thin volumes.
  Restored volume group snapper_thinp

Version-Release number of selected component (if applicable):
3.8.0-0.40.el7.x86_64

lvm2-2.02.99-0.28.el7    BUILT: Fri May  3 09:12:57 CDT 2013
lvm2-libs-2.02.99-0.28.el7    BUILT: Fri May  3 09:12:57 CDT 2013
lvm2-cluster-2.02.99-0.28.el7    BUILT: Fri May  3 09:12:57 CDT 2013
device-mapper-1.02.78-0.28.el7    BUILT: Fri May  3 09:12:57 CDT 2013
device-mapper-libs-1.02.78-0.28.el7    BUILT: Fri May  3 09:12:57 CDT 2013
device-mapper-event-1.02.78-0.28.el7    BUILT: Fri May  3 09:12:57 CDT 2013
device-mapper-event-libs-1.02.78-0.28.el7    BUILT: Fri May  3 09:12:57 CDT 2013
cmirror-2.02.99-0.28.el7    BUILT: Fri May  3 09:12:57 CDT 2013


How reproducible:
Everytime

Current support for vgcfgrestore of metadata containing thin pools is very limited, and should be used very carefully.

Since we cannot guarantee, the user's restore will not destroy his pool metadata, we have put in some limited support, which requires usage of  '--force' and user should be really thinking more then twice before he will use this command.

If the restore is being done purely because of restore of some non-thin related LV - everything should go as normal restore. However for thin pool restore, we are missing tool, to do some analysis between kernel metadata and restore lvm2 metadata and think about what best we can do, to get both into reasonably matching state. So far there is no such support - thus we require to use '-f'.