Hide Forgot
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.
Marking verified with latest rpms. Thin pool regression testing passed without hitting transaction_id issues.
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