Bug 1125275

Summary: [abrt] btrfs-progs: close_ctree(): btrfsck killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Wilhelm.Buchmueller
Component: btrfs-progsAssignee: Josef Bacik <josef>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: esandeen, josef, mmahut
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5d57894f6b7d154a33e45a0d7a2ec3315ad97058
Whiteboard: abrt_hash:d3c28757da4652079baec5db787cd280272d98de
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 21:52:31 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 Wilhelm.Buchmueller 2014-07-31 13:20:53 UTC 
Description of problem:
check an damaged filesys (created by an Fedora20 installation)

Version-Release number of selected component:
btrfs-progs-3.14.2-3.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        btrfsck -b /dev/sdd2
crash_function: close_ctree
executable:     /usr/sbin/btrfsck
kernel:         3.15.6-200.fc20.i686+PAE
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (2 frames)
 #0 close_ctree at disk-io.c:1370
 #1 cmd_check at cmds-check.c:6667
Comment 1 Wilhelm.Buchmueller 2014-07-31 13:20:59 UTC 
Created attachment 922918 [details]
File: backtrace
Comment 2 Wilhelm.Buchmueller 2014-07-31 13:21:01 UTC 
Created attachment 922919 [details]
File: cgroup
Comment 3 Wilhelm.Buchmueller 2014-07-31 13:21:03 UTC 
Created attachment 922920 [details]
File: core_backtrace
Comment 4 Wilhelm.Buchmueller 2014-07-31 13:21:05 UTC 
Created attachment 922921 [details]
File: dso_list
Comment 5 Wilhelm.Buchmueller 2014-07-31 13:21:07 UTC 
Created attachment 922922 [details]
File: environ
Comment 6 Wilhelm.Buchmueller 2014-07-31 13:21:09 UTC 
Created attachment 922923 [details]
File: exploitable
Comment 7 Wilhelm.Buchmueller 2014-07-31 13:21:11 UTC 
Created attachment 922924 [details]
File: limits
Comment 8 Wilhelm.Buchmueller 2014-07-31 13:21:13 UTC 
Created attachment 922925 [details]
File: maps
Comment 9 Wilhelm.Buchmueller 2014-07-31 13:21:15 UTC 
Created attachment 922926 [details]
File: open_fds
Comment 10 Wilhelm.Buchmueller 2014-07-31 13:21:17 UTC 
Created attachment 922927 [details]
File: proc_pid_status
Comment 11 Wilhelm.Buchmueller 2014-07-31 13:21:19 UTC 
Created attachment 922928 [details]
File: var_log_messages
Comment 12 Eric Sandeen 2014-07-31 15:18:36 UTC 
If a btrfs-image filesystem image reproduces this, that might be helpful information to gather.

Thanks,
-Eric
Comment 13 Fedora End Of Life 2015-05-29 12:31:40 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Fedora End Of Life 2015-06-29 21:52:31 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.