Red Hat Bugzilla – Bug 1275098
[abrt] device-mapper-event: _timeout_thread(): dmeventd killed by SIGSEGV
Last modified: 2016-11-04 00:12:07 EDT
Version-Release number of selected component:
cmdline: /usr/sbin/dmeventd -f
Thread no. 1 (1 frames)
#0 _timeout_thread at dmeventd.c:582
Potential duplicate: bug 1220856
Created attachment 1086287 [details]
Created attachment 1086288 [details]
Created attachment 1086289 [details]
Created attachment 1086290 [details]
Created attachment 1086291 [details]
Created attachment 1086292 [details]
Created attachment 1086293 [details]
Created attachment 1086294 [details]
Created attachment 1086295 [details]
Created attachment 1086296 [details]
Created attachment 1086297 [details]
dmeventd has been redesigned and new code already went upstream.
Once we will have new package ready - we will ask for revaluation.
Old version had many design problems that has been addressed by new rewrite.
Common bug has been parallel work in libdm and lib lvm2 code.
I believe this is fixed with recent commits in dmeventd code in lvm2 2.02.133.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see firstname.lastname@example.org with any questions
Marking verified (SanityOnly) like mentioned in comment #17. I have not seen
this issue during the regression test runs.
lvm2-2.02.165-2.el7 BUILT: Wed Sep 14 09:01:43 CDT 2016
lvm2-libs-2.02.165-2.el7 BUILT: Wed Sep 14 09:01:43 CDT 2016
lvm2-cluster-2.02.165-2.el7 BUILT: Wed Sep 14 09:01:43 CDT 2016
device-mapper-1.02.134-2.el7 BUILT: Wed Sep 14 09:01:43 CDT 2016
device-mapper-libs-1.02.134-2.el7 BUILT: Wed Sep 14 09:01:43 CDT 2016
device-mapper-event-1.02.134-2.el7 BUILT: Wed Sep 14 09:01:43 CDT 2016
device-mapper-event-libs-1.02.134-2.el7 BUILT: Wed Sep 14 09:01:43 CDT 2016
device-mapper-persistent-data-0.6.3-1.el7 BUILT: Fri Jul 22 05:29:13 CDT
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.