Bug 1089022

Summary: [abrt] btrfs-progs: count_csum_range(): btrfsck killed by SIGABRT
Product: [Fedora] Fedora Reporter: Maxim Galaganov <voltage>
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/5b1ced12e97d4b16dd5c0a7aed6c5a0d6e0a2f45
Whiteboard: abrt_hash:65137b7ff70a27ff1254d3317a01310931c6cf65
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:09:33 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 Maxim Galaganov 2014-04-17 17:09:08 UTC
Description of problem:
trying to btrfsck on ssd drive after certain parent transid verify failed that prevent me to boot

Version-Release number of selected component:
btrfs-progs-3.12-1.fc20

Additional info:
reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        btrfsck /dev/sdb3
crash_function: count_csum_range
executable:     /usr/sbin/btrfsck
kernel:         3.13.9-200.fc20.x86_64
runlevel:       3 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (7 frames)
 #4 count_csum_range at cmds-check.c:1074
 #5 process_file_extent at cmds-check.c:1186
 #6 process_one_leaf at cmds-check.c:1248
 #7 walk_down_tree at cmds-check.c:1325
 #8 check_fs_root at cmds-check.c:1927
 #9 check_fs_roots at cmds-check.c:2008
 #10 cmd_check at cmds-check.c:6162

Comment 1 Maxim Galaganov 2014-04-17 17:09:13 UTC
Created attachment 887213 [details]
File: backtrace

Comment 2 Maxim Galaganov 2014-04-17 17:09:15 UTC
Created attachment 887214 [details]
File: cgroup

Comment 3 Maxim Galaganov 2014-04-17 17:09:17 UTC
Created attachment 887215 [details]
File: core_backtrace

Comment 4 Maxim Galaganov 2014-04-17 17:09:20 UTC
Created attachment 887216 [details]
File: dso_list

Comment 5 Maxim Galaganov 2014-04-17 17:09:22 UTC
Created attachment 887217 [details]
File: environ

Comment 6 Maxim Galaganov 2014-04-17 17:09:24 UTC
Created attachment 887218 [details]
File: limits

Comment 7 Maxim Galaganov 2014-04-17 17:09:26 UTC
Created attachment 887219 [details]
File: maps

Comment 8 Maxim Galaganov 2014-04-17 17:09:28 UTC
Created attachment 887220 [details]
File: open_fds

Comment 9 Maxim Galaganov 2014-04-17 17:09:30 UTC
Created attachment 887221 [details]
File: proc_pid_status

Comment 10 Maxim Galaganov 2014-04-17 17:09:32 UTC
Created attachment 887222 [details]
File: var_log_messages

Comment 11 Eric Sandeen 2014-05-13 16:39:03 UTC
btrfs-progs-3.14.1 has been pushed to Fedora 19 and 20 for testing.

I frankly have no idea if this will resolve your bug or not, but if you test it and find that it does, please take the opportunity to close this bug.  :)

Thanks,
-Eric

Comment 12 Fedora End Of Life 2015-05-29 11:36:20 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 13 Fedora End Of Life 2015-06-29 20:09:33 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.