Description of problem: BTRFS crashed on my system. The crash was not reportable so I posted on the users list (http://thread.gmane.org/gmane.linux.redhat.fedora.general/461602). While diagnosing the crash, I ran btrfs check which core dumped. I do not know how to further debug this. I can provide more info if someone is wiling to guide me. Version-Release number of selected component: btrfs-progs-4.2.1-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: btrfs check /dev/sda1 crash_function: add_tree_backref executable: /usr/sbin/btrfs global_pid: 4498 kernel: 4.2.3-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (5 frames) #2 add_tree_backref at cmds-check.c:4481 #3 add_root_to_pending at cmds-check.c:6026 #4 deal_root_from_list at cmds-check.c:7880 #5 check_chunks_and_extents at cmds-check.c:8050 #6 cmd_check at cmds-check.c:9478
Created attachment 1084429 [details] File: backtrace
Created attachment 1084430 [details] File: cgroup
Created attachment 1084431 [details] File: core_backtrace
Created attachment 1084432 [details] File: dso_list
Created attachment 1084433 [details] File: environ
Created attachment 1084434 [details] File: limits
Created attachment 1084435 [details] File: maps
Created attachment 1084436 [details] File: mountinfo
Created attachment 1084437 [details] File: namespaces
Created attachment 1084438 [details] File: open_fds
Created attachment 1084439 [details] File: proc_pid_status
Created attachment 1084440 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.