Bug 1069764

Summary: [abrt] lvm2: daemon_log(): lvmetad killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Michael Hampton <error>
Component: lvm2Assignee: Petr Rockai <prockai>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: agk, bmarzins, bmr, chris.kjeldgaard, dwysocha, heinzm, jonathan, lvm-team, msnitzer, prajnoha, prockai, zkabelac
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5123ce4adc0975e22456b01014de5d9c5ea85646
Whiteboard: abrt_hash:3dc4c7703d2ef9a49a108af77973d69599067a59
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-09 00:36:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Michael Hampton 2014-02-25 15:48:52 UTC 
Version-Release number of selected component:
lvm2-2.02.103-5.fc20

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/sbin/lvmetad
crash_function: daemon_log
executable:     /usr/sbin/lvmetad
kernel:         3.13.3-201.fc20.x86_64
runlevel:       unknown
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 daemon_log at daemon-log.c:54
 #1 daemon_logf at daemon-log.c:76
 #2 pv_clear_all at lvmetad-core.c:829
 #3 handler at lvmetad-core.c:1094
 #4 client_thread at daemon-server.c:401
Comment 1 Michael Hampton 2014-02-25 15:48:58 UTC 
Created attachment 867483 [details]
File: backtrace
Comment 2 Michael Hampton 2014-02-25 15:49:03 UTC 
Created attachment 867484 [details]
File: cgroup
Comment 3 Michael Hampton 2014-02-25 15:49:14 UTC 
Created attachment 867485 [details]
File: core_backtrace
Comment 4 Michael Hampton 2014-02-25 15:49:15 UTC 
Created attachment 867486 [details]
File: dso_list
Comment 5 Michael Hampton 2014-02-25 15:49:19 UTC 
Created attachment 867487 [details]
File: environ
Comment 6 Michael Hampton 2014-02-25 15:49:21 UTC 
Created attachment 867488 [details]
File: exploitable
Comment 7 Michael Hampton 2014-02-25 15:49:22 UTC 
Created attachment 867489 [details]
File: limits
Comment 8 Michael Hampton 2014-02-25 15:49:24 UTC 
Created attachment 867490 [details]
File: maps
Comment 9 Michael Hampton 2014-02-25 15:49:26 UTC 
Created attachment 867491 [details]
File: open_fds
Comment 10 Michael Hampton 2014-02-25 15:49:28 UTC 
Created attachment 867492 [details]
File: proc_pid_status
Comment 11 Michael Hampton 2014-02-25 15:49:32 UTC 
Created attachment 867493 [details]
File: var_log_messages
Comment 12 Petr Rockai 2014-02-28 11:06:27 UTC 
Seems like a client thread is still trying to log while lvmetad is shutting down. We probably need to clean up worker threads before going into shutdown. The log seems to be related to #1069808 so that part of the problem should be already sorted out. (Seems like the user tried to obey that message, restarted lvmetad and it got a SEGV during shutdown as there was still traffic going in.)
Comment 13 Petr Rockai 2014-06-09 00:36:45 UTC 
Should be fixed upstream in 488f3085279e24af21e870d5a74d0953094552f7. The shutdown sequence now waits for client threads to finish before destroying resources (which they may be using).
Comment 14 Peter Rajnoha 2014-06-09 07:10:02 UTC 
The patch is part of upcoming lvm2 v2.02.107 release.