Bug 1059589

Summary: [abrt] gvfs: verify_metadata_block(): gvfsd-metadata killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Vratislav Podzimek <vpodzime>
Component: gvfsAssignee: Ondrej Holy <oholy>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: alexl, bart, Bengt.Lueers, bnocera, dragomir.dan, ebirman77, fonya, gczarcinski, herve, jcmj, mastaizawfm, moez.roy, nalimilan, ndatrick, nilu_lal, oholy, pal666, redhatbugzilla, sarrab1976, szoke.karcsi, torel, unix.soul, wincc, wotlitn, yanglifu90
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ff59df221baacac30f60dfc7cf2825d50967b5d5
Whiteboard: abrt_hash:720703d73a4b64a1b38ad8863a8b7f5961d14dd9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-15 14:42:06 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 Vratislav Podzimek 2014-01-30 08:52:55 UTC 
Version-Release number of selected component:
gvfs-1.18.3-2.fc20

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/libexec/gvfsd-metadata
crash_function: verify_metadata_block
executable:     /usr/libexec/gvfsd-metadata
kernel:         3.12.8-300.fc20.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 verify_metadata_block at metatree.c:186
 #1 copy_tree_to_builder at metatree.c:2123
 #2 meta_tree_flush_locked at metatree.c:2293
 #3 meta_tree_flush at metatree.c:2315
 #4 writeout_timeout at meta-daemon.c:62

Potential duplicate: bug 699109
Comment 1 Vratislav Podzimek 2014-01-30 08:53:05 UTC 
Created attachment 857380 [details]
File: backtrace
Comment 2 Vratislav Podzimek 2014-01-30 08:53:15 UTC 
Created attachment 857381 [details]
File: cgroup
Comment 3 Vratislav Podzimek 2014-01-30 08:53:19 UTC 
Created attachment 857382 [details]
File: core_backtrace
Comment 4 Vratislav Podzimek 2014-01-30 08:53:21 UTC 
Created attachment 857383 [details]
File: dso_list
Comment 5 Vratislav Podzimek 2014-01-30 08:53:23 UTC 
Created attachment 857384 [details]
File: environ
Comment 6 Vratislav Podzimek 2014-01-30 08:53:31 UTC 
Created attachment 857385 [details]
File: exploitable
Comment 7 Vratislav Podzimek 2014-01-30 08:53:33 UTC 
Created attachment 857386 [details]
File: limits
Comment 8 Vratislav Podzimek 2014-01-30 08:53:35 UTC 
Created attachment 857387 [details]
File: maps
Comment 9 Vratislav Podzimek 2014-01-30 08:53:44 UTC 
Created attachment 857388 [details]
File: open_fds
Comment 10 Vratislav Podzimek 2014-01-30 08:53:46 UTC 
Created attachment 857389 [details]
File: proc_pid_status
Comment 11 Vratislav Podzimek 2014-01-30 08:53:53 UTC 
Created attachment 857390 [details]
File: var_log_messages
Comment 12 Bart Ratgers 2014-06-19 16:13:28 UTC 
Another user experienced a similar problem:

Unknown	

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/gvfsd-metadata
crash_function: verify_metadata_block
executable:     /usr/libexec/gvfsd-metadata
kernel:         3.14.7-200.fc20.x86_64
package:        gvfs-1.18.3-2.fc20
reason:         gvfsd-metadata killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Vratislav Podzimek 2014-08-13 07:56:52 UTC 
Guys, are ever going to do something with this bug? I just see more and more people appearing in the CC list (i.e. hitting the issue) and it's been here for a while.
Comment 14 Vratislav Podzimek 2014-08-13 07:59:44 UTC 
And the duplicate bug on Fedora 18 has been here for even much, much longer.
Comment 15 Ondrej Holy 2014-08-15 14:42:06 UTC 
We know about the bug and we keep track on it, however we need a reproducer with empty metadata database. See for the detailed instruction:
https://bugzilla.redhat.com/show_bug.cgi?id=699109#c74

*** This bug has been marked as a duplicate of bug 699109 ***