Version-Release number of selected component:
cmdline: /usr/sbin/dmeventd -f
Thread no. 1 (1 frames)
Potential duplicate: bug 1220856
Created attachment 1148404 [details]
Created attachment 1148405 [details]
Created attachment 1148406 [details]
Created attachment 1148407 [details]
Created attachment 1148408 [details]
Created attachment 1148409 [details]
Created attachment 1148410 [details]
Created attachment 1148411 [details]
Created attachment 1148412 [details]
Created attachment 1148413 [details]
Created attachment 1148414 [details]
Created attachment 1148415 [details]
Created attachment 1148417 [details]
Currently, we have lvm2-2.02.152-2.el7 in 7.3 - please try this build and see if you can reproduce. Thanks.
(In reply to Peter Rajnoha from comment #17)
> Currently, we have lvm2-2.02.152-2.el7 in 7.3 - please try this build and
> see if you can reproduce. Thanks.
You mean, lvm2-2.02.156-1, right?
"or whatever later version we built since"
For now, I'm assuming this is fixed with recent builds. If this problem appears again, please, reopen this bug report.
Adding QA ack for 7.3. SanityOnly, it's unlikely we'll be able to reproduce this. We can verify this bug after regression run is done without any dmeventd segfaults.
Verified - SanityOnly.
The issue did not occur during regression testing.
lvm2-2.02.165-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016
lvm2-libs-2.02.165-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016
lvm2-cluster-2.02.165-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016
device-mapper-1.02.134-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016
device-mapper-libs-1.02.134-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016
device-mapper-event-1.02.134-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016
device-mapper-event-libs-1.02.134-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016
device-mapper-persistent-data-0.6.3-1.el7 BUILT: Fri Jul 22 12:29:13 CEST 2016
cmirror-2.02.165-2.el7 BUILT: Wed Sep 14 16:01:43 CEST 2016
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.