Bug 1099224

Summary: [abrt] btrfs-progs-3.14.1-1.fc20: process_extent_buffer: Process /usr/sbin/btrfs was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Matt Hooper <matthew.hooper>
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: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ba069109398bb7823f5cf09e6502a399a73e0ebd
Whiteboard: abrt_hash:6b3ee24da28f7da5309e0c491a2ba4aef16f1d57
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:43:23 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Matt Hooper 2014-05-19 19:38:14 UTC
Version-Release number of selected component:
btrfs-progs-3.14.1-1.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        btrfs rescue chunk -v -y /dev/mapper/luks-283a637d-3382-47a3-bd70-4956060c9a19 /dev/mapper/luks-51102b55-d0d2-474e-a2d1-d6efa557a20f /dev/mapper/luks-ee66a1db-ed20-48e1-809b-1e0ade2dfec0 /dev/mapper/luks-d0568fb6-1e41-404e-a4a2-a8cfd9ba7e8f
crash_function: process_extent_buffer
executable:     /usr/sbin/btrfs
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (2 frames)
 #4 process_extent_buffer at chunk-recover.c:131
 #5 scan_one_device at chunk-recover.c:780

Comment 1 Matt Hooper 2014-05-19 19:38:19 UTC
Created attachment 897300 [details]
File: backtrace

Comment 2 Matt Hooper 2014-05-19 19:38:21 UTC
Created attachment 897301 [details]
File: cgroup

Comment 3 Matt Hooper 2014-05-19 19:38:23 UTC
Created attachment 897302 [details]
File: core_backtrace

Comment 4 Matt Hooper 2014-05-19 19:38:25 UTC
Created attachment 897303 [details]
File: dso_list

Comment 5 Matt Hooper 2014-05-19 19:38:27 UTC
Created attachment 897304 [details]
File: environ

Comment 6 Matt Hooper 2014-05-19 19:38:29 UTC
Created attachment 897305 [details]
File: limits

Comment 7 Matt Hooper 2014-05-19 19:38:31 UTC
Created attachment 897306 [details]
File: maps

Comment 8 Matt Hooper 2014-05-19 19:38:33 UTC
Created attachment 897307 [details]
File: open_fds

Comment 9 Matt Hooper 2014-05-19 19:38:35 UTC
Created attachment 897308 [details]
File: proc_pid_status

Comment 10 Matt Hooper 2014-05-19 19:38:37 UTC
Created attachment 897309 [details]
File: var_log_messages

Comment 11 Eric Sandeen 2014-05-19 20:35:36 UTC
*** Bug 1098798 has been marked as a duplicate of this bug. ***

Comment 12 Matt Hooper 2014-06-17 18:30:06 UTC
Any ideas on this? I'd like to recover the data from the disks if possible.

Does the chunk recover command make changes as it goes? What I mean is are things being recovered up to the point of the assert, so each time it is run its actually starting from a different point, or does it work out what needs to be changed and apply at the end which it doesn't reach due to the assert?

Comment 13 Fedora End Of Life 2015-05-29 11:53:55 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 20:43:23 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.