Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionHeinz Mauelshagen
2020-01-14 14:11:05 UTC
Description of problem:
After a bunch of snapshot creations and deletions (each 30 snapshots of 2 origins), kernel and userspace transaction ids differed by 2 thus preventing further pool updates, also pool and hence thin reactivations don't work.
Version-Release number of selected component (if applicable):
How reproducible:
Create/remove snapshots as described above.
Steps to Reproduce:
1.
2.
3.
Actual results:
# lvremove rhel_bp-07/rhel-7_group-0_node-0
Thin pool rhel_bp--07-vm_pool-tpool (253:23) transaction_id is 391, while expected 392.
Failed to suspend rhel_bp-07/vm_pool with queued messages.
Failed to update pool rhel_bp-07/vm_pool.
Also creation of new snapshot fail alike.
Expected results:
lv(create|remove) of thin snapshots work.
Additional info:
Relative to uspace and kspace transaction differing, see related https://bugzilla.redhat.com/show_bug.cgi?id=1069364.
Kernel log example of failed creation:
[5447619.705068] device-mapper: thin: Creation of new snapshot 11 of device 1 failed.
[5447620.934856] device-mapper: table: 253:46: thin: Couldn't open thin internal device
Comment 1Heinz Mauelshagen
2020-01-14 14:13:27 UTC
This patch is now upstream:
https://listman.redhat.com/archives/lvm-devel/2021-March/msg00102.html
Under some circumstances it might be giving the observed behavior as lvm2 might
have tried to submit creation and destruction of same pool due to this reverted test.
Moving to post state - the race likely must have been very hard to hit even before.
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 (lvm2 bug fix and enhancement update), 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-2021:4431