Description of problem: 1. Doing a backup with rdiffbackup to an external USB btrfs HDD. 2. Putting the computer to sleep/suspend/hibernate (I do not know the exact differences) during the backup. 3. Waking the computer up. Additional info: reporter: libreport-2.2.2 WARNING: CPU: 3 PID: 31028 at fs/btrfs/super.c:257 __btrfs_abort_transaction+0x50/0x110 [btrfs]() Modules linked in: btrfs raid6_pq xor usblp fuse ipt_MASQUERADE xt_CHECKSUM tun ip6t_rpfilter bnep bluetooth 6lowpan_iphc ip6t_REJECT xt_conntrack cfg80211 rfkill ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw coretemp iTCO_wdt iTCO_vendor_support gpio_ich ppdev kvm_intel snd_hda_codec_realtek kvm snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel lpc_ich microcode snd_hda_codec serio_raw snd_hwdep asus_atk0110 atl1 mii i2c_i801 snd_seq snd_seq_device parport_pc snd_pcm acpi_cpufreq parport shpchp mfd_core snd_timer snd soundcore usb_storage radeon i2c_algo_bit drm_kms_helper ttm drm ata_generic pata_acpi i2c_core CPU: 3 PID: 31028 Comm: btrfs-endio-wri Not tainted 3.14.4-200.fc20.x86_64 #1 Hardware name: System manufacturer System Product Name/P5B-MX, BIOS 0704 06/26/2008 0000000000000000 00000000eb506eff ffff88003e57dbd8 ffffffff816ef1d2 ffff88003e57dc20 ffff88003e57dc10 ffffffff8108a1bd 00000000fffffffb ffff8800597b7000 ffff8800178a8640 ffffffffa0696c40 0000000000000a9a Call Trace: [<ffffffff816ef1d2>] dump_stack+0x45/0x56 [<ffffffff8108a1bd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8108a23c>] warn_slowpath_fmt+0x5c/0x80 [<ffffffffa05f3030>] __btrfs_abort_transaction+0x50/0x110 [btrfs] [<ffffffffa060edba>] btrfs_run_delayed_refs.part.60+0x12a/0x280 [btrfs] [<ffffffffa060ef27>] btrfs_run_delayed_refs+0x17/0x20 [btrfs] [<ffffffffa062043b>] __btrfs_end_transaction+0x23b/0x360 [btrfs] [<ffffffffa0620570>] btrfs_end_transaction+0x10/0x20 [btrfs] [<ffffffffa0628301>] btrfs_finish_ordered_io+0x141/0x5a0 [btrfs] [<ffffffffa06289f5>] finish_ordered_fn+0x15/0x20 [btrfs] [<ffffffffa064e4d4>] worker_loop+0x144/0x540 [btrfs] [<ffffffffa064e390>] ? btrfs_queue_worker+0x2f0/0x2f0 [btrfs] [<ffffffff810ae211>] kthread+0xe1/0x100 [<ffffffff810ae130>] ? insert_kthread_work+0x40/0x40 [<ffffffff816ff4bc>] ret_from_fork+0x7c/0xb0 [<ffffffff810ae130>] ? insert_kthread_work+0x40/0x40
Created attachment 900778 [details] File: dmesg
See also bug #1109563.
This bug might be related to: Bug 987281 - [abrt] gvfs-1.16.3-2.fc19: g_malloc: Process /usr/libexec/gvfs-udisks2-volume-monitor was killed by signal 11 (SIGSEGV) Bug 929436 - [abrt] gvfs-1.15.4-2.fc19: unmount_cb: Process /usr/libexec/gvfs-udisks2-volume-monitor was killed by signal 11 (SIGSEGV)
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.