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.
Description of problem:
Logical volume creation fails with the below error:
# lvcreate -s -kn --name snap_pulp sat6vg/pulp
Thin pool sat6vg-thinpool-tpool (253:16) transaction_id is 1302, while expected 1303.
Failed to suspend and send message sat6vg/thinpool.
Suspect issue is due to metadata resize
Version-Release number of selected component (if applicable):
lvm2-2.02.130-5.el7_2.2.x86_64
device-mapper-1.02.107-5.el7_2.2.x86_64
kernel-3.10.0-327.18.2.el7.x86_64
Local reproduction unsuccessful so far.
Expected results:
transaction_id should not become mis-aligned
Additional info:
Data attached
I'm convinced this bug is now handled better via Bug 1199837.
Bug should be tried to reproduce with version 2.02.165.
There were couple major improvements on messaging to thin-pool,
so this 'transactionId' mismatch should no longer be possible to hit with 'common' usage of lvm2.
-
As for this BZ - in the archive dir there are visible commands with 'locking_type=0' - this locking_type shell not be used in any common scenario - it's not supportable and might have very unexpectable side-effects.
It seems removal of 'lvremove sat6vg/snap_mongodb' possibly caused an issue where update of lvm2 was not possible ? (reboot/mounted volume ?)
Anywya - BZ should be tried to reproduce with latest version - since it should diagnose any problem right in the moment it happens, instead of postponing the issue to rise-up with some later command.
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-2017:2222