Description of problem: This disk is my backup disk. I was having trouble deleting some folders, the filesystem would turn read-only out of the blue. So I unmounted, and ran `btrfs-check` which core dumps. # btrfs check -p /dev/sdd1 Checking filesystem on /dev/sdd1 UUID: c75861ea-09f8-4e70-9db5-a6c5f6539af8 Aborted (core dumped) When the filesystem turned read-only, I looked in the journal and I see errors like these: Sep 03 21:18:41 hostname kernel: BTRFS info (device sdd1): forced readonly Sep 03 21:18:41 hostname kernel: BTRFS: error (device sdd1) in update_ref_for_cow:1014: errno=-30 Readonly filesystem Sep 03 21:18:41 hostname kernel: ---[ end trace d7224e52feb03ef7 ]--- Sep 03 21:18:41 hostname kernel: [<ffffffff817dae72>] entry_SYSCALL_64_fastpath+0x1a/0xa4 Sep 03 21:18:41 hostname kernel: [<ffffffff812594cb>] SyS_unlinkat+0x1b/0x30 Sep 03 21:18:41 hostname kernel: [<ffffffff81258a8b>] do_unlinkat+0x25b/0x2b0 Sep 03 21:18:41 hostname kernel: [<ffffffff81254ba1>] vfs_unlink+0xf1/0x190 Sep 03 21:18:41 hostname kernel: [<ffffffffc077efbb>] btrfs_unlink+0x6b/0xb0 [btrfs] Sep 03 21:18:41 hostname kernel: [<ffffffffc077ef2c>] btrfs_unlink_inode+0x1c/0x40 [btrfs] Sep 03 21:18:41 hostname kernel: [<ffffffffc077b435>] __btrfs_unlink_inode+0xb5/0x460 [btrfs] Sep 03 21:18:41 hostname kernel: [<ffffffffc0766d08>] btrfs_lookup_dir_item+0x78/0xc0 [btrfs] Sep 03 21:18:41 hostname kernel: [<ffffffffc074e116>] btrfs_search_slot+0x1e6/0x9b0 [btrfs] Sep 03 21:18:41 hostname kernel: [<ffffffffc074a522>] btrfs_cow_block+0x112/0x1d0 [btrfs] Sep 03 21:18:41 hostname kernel: [<ffffffffc074a02f>] __btrfs_cow_block+0x22f/0x590 [btrfs] Sep 03 21:18:41 hostname kernel: [<ffffffffc079afed>] ? copy_extent_buffer+0xad/0x110 [btrfs] Sep 03 21:18:41 hostname kernel: [<ffffffffc0749ca3>] update_ref_for_cow+0x203/0x360 [btrfs] Sep 03 21:18:41 hostname kernel: [<ffffffffc0758cfc>] btrfs_lookup_extent_info+0x3ec/0x490 [btrfs] Sep 03 21:18:41 hostname kernel: [<ffffffff810a750d>] warn_slowpath_null+0x1d/0x20 Sep 03 21:18:41 hostname kernel: [<ffffffff810a73db>] __warn+0xcb/0xf0 Sep 03 21:18:41 hostname kernel: [<ffffffff813d954e>] dump_stack+0x63/0x85 Sep 03 21:18:41 hostname kernel: Call Trace: Sep 03 21:18:41 hostname kernel: 000003ad000000a3 ffff8800c7a4f098 ffff880095c693f0 ffff8800c7a4f098 Sep 03 21:18:41 hostname kernel: 0000000000000000 0000000000000000 ffff88016f2dfa98 ffffffff810a73db Sep 03 21:18:41 hostname kernel: 0000000000000286 000000005671d908 ffff88016f2dfa58 ffffffff813d954e Sep 03 21:18:41 hostname kernel: Hardware name: LENOVO 20ALCTO1WW/20ALCTO1WW, BIOS GIET66WW (2.16 ) 12/02/2013 Sep 03 21:18:41 hostname kernel: CPU: 0 PID: 10423 Comm: rm Tainted: P W OE 4.6.7-200.fc23.x86_64 #1 Sep 03 21:18:41 hostname kernel: snd_hda_codec_hdmi snd_hda_codec_generic videodev snd_hda_intel iwlwifi snd_hda_codec joydev snd_hda_core rtsx_pci_ms cfg80211 snd_hwdep lpc_ich medi Sep 03 21:18:41 hostname kernel: Modules linked in: ses enclosure scsi_transport_sas uas usb_storage tun snd_usb_audio snd_usbmidi_lib snd_rawmidi ccm ip6t_REJECT nf_reject_ipv6 ip6t_ Sep 03 21:18:41 hostname kernel: WARNING: CPU: 0 PID: 10423 at fs/btrfs/extent-tree.c:941 btrfs_lookup_extent_info+0x3ec/0x490 [btrfs] Version-Release number of selected component: btrfs-progs-4.4.1-1.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: btrfs check -p /dev/sdd1 crash_function: add_tree_backref executable: /usr/sbin/btrfs global_pid: 13558 kernel: 4.6.7-200.fc23.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (5 frames) #2 add_tree_backref at cmds-check.c:4663 #3 run_next_block at cmds-check.c:6195 #4 deal_root_from_list at cmds-check.c:8108 #5 check_chunks_and_extents at cmds-check.c:8275 #6 cmd_check at cmds-check.c:9721
Created attachment 1197453 [details] File: backtrace
Created attachment 1197454 [details] File: cgroup
Created attachment 1197455 [details] File: core_backtrace
Created attachment 1197456 [details] File: dso_list
Created attachment 1197457 [details] File: environ
Created attachment 1197458 [details] File: limits
Created attachment 1197459 [details] File: maps
Created attachment 1197460 [details] File: mountinfo
Created attachment 1197461 [details] File: namespaces
Created attachment 1197462 [details] File: open_fds
Created attachment 1197463 [details] File: proc_pid_status
Created attachment 1197464 [details] File: var_log_messages
I would suggest grabbing the latest src.rpm from https://kojipkgs.fedoraproject.org/packages/btrfs-progs/4.7.1/1.fc26/src/btrfs-progs-4.7.1-1.fc26.src.rpm and run rpmbuild --rebuild on that, then upgrade to the resulting btrfs-progs. If the bug persists, please report it on the upstream btrfs list at linux-btrfs.org Josef generally doesn't respond to fedora bugs filed here. Thanks, -Eric
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.