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:
Activating thinp snapshots fails.

Version-Release number of selected component (if applicable):
Fedora 22 (all updates)

How reproducible:
always

Steps to Reproduce:
1. Install F22 with thinp layout
1.a reboot
1.b login
2. in the same pool:

lvcreate --thin --virtualsize 2629415424B --name Image-1.0 fedora/pool00

lvchange --activate y fedora/Image-1.0 --ignoreactivationskip
lvchange --activate n fedora/Image-1.0
# ^^ If you skip the two lines above, then the bug is not triggered

lvcreate --snapshot --name fedora/Image-1.1 fedora/Image-1.0
lvchange --activate y fedora/Image-1.1 --ignoreactivationskip
# ^^ Fails

Actual results:
# lvchange --activate y fedora/Image-1.1 --ignoreactivationskip
  device-mapper: reload ioctl on  failed: No data available
#

Expected results:
# lvchange --activate y fedora/Image-1.1 --ignoreactivationskip
#

Additional info:
Workaround is to enable the parent before:
# lvchange --activate y fedora/Image-1.0 --ignoreactivationskip
# lvchange --activate y fedora/Image-1.1 --ignoreactivationskip
# 

-vvvv output:
https://paste.fedoraproject.org/227816/33185971/

This is also reproducible on RHEL 7.

Created attachment 1037334 [details]
Experimental patch

Adding initial version of patch to fight with ordering of messaging to thin-pool.

It has in fact appeared to be a more complex problem how to deal with error states.

Current proposal moves message sending from 'resume' phase to 'suspend' phase.
Resume always resume thin-pool 'as-is' and only validates transaction_id.

The patch itself does not yet improve of error paths and possible automatic fixing of 'easy-to-fix issues' - will follow later possibly, but with this switched order it will get fairly easier since it will not leave thin-pool suspend when we detect some error in the middle of message creation.

Updated patch is now upstream  (lvm 2.02.124)

https://www.redhat.com/archives/lvm-devel/2015-July/msg00015.html

But it still left couple issue for resolving.
Complexity with some pool online renaming for external users got a bit more complicated so still some further patches are needed and are under development and testing.

Fixed upstream for a while.
Surely a member of 2.02.130.