Hide Forgot
Version-Release number of selected component: device-mapper-event-1.02.107-5.el7_2.1 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/sbin/dmeventd -f crash_function: _timeout_thread executable: /usr/sbin/dmeventd global_pid: 1047 kernel: 3.10.0-377.el7.x86_64 runlevel: unknown type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (1 frames) #0 _timeout_thread Potential duplicate: bug 1220856
Created attachment 1148404 [details] File: backtrace
Created attachment 1148405 [details] File: cgroup
Created attachment 1148406 [details] File: core_backtrace
Created attachment 1148407 [details] File: dso_list
Created attachment 1148408 [details] File: environ
Created attachment 1148409 [details] File: exploitable
Created attachment 1148410 [details] File: limits
Created attachment 1148411 [details] File: machineid
Created attachment 1148412 [details] File: maps
Created attachment 1148413 [details] File: open_fds
Created attachment 1148414 [details] File: proc_pid_status
Created attachment 1148415 [details] File: var_log_messages
Created attachment 1148417 [details] File: sosreport.tar.xz
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. 3.10.0-505.el7.x86_64 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. https://rhn.redhat.com/errata/RHBA-2016-1445.html