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
Created attachment 887213 [details] File: backtrace
Created attachment 887214 [details] File: cgroup
Created attachment 887215 [details] File: core_backtrace
Created attachment 887216 [details] File: dso_list
Created attachment 887217 [details] File: environ
Created attachment 887218 [details] File: limits
Created attachment 887219 [details] File: maps
Created attachment 887220 [details] File: open_fds
Created attachment 887221 [details] File: proc_pid_status
Created attachment 887222 [details] File: var_log_messages
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
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.
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.