Description of problem: This bugs occurs during file transfert to an usb3 external hard drive. The external hard drive format is btrfs. Additional info: reporter: libreport-2.2.2 WARNING: CPU: 3 PID: 2050 at fs/btrfs/inode.c:866 cow_file_range+0x438/0x450 [btrfs]() Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache bnep bluetooth 6lowpan_iphc ip6t_rpfilter ip6t_REJECT cfg80211 xt_conntrack 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 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm mxm_wmi x86_pkg_temp_thermal eeepc_wmi coretemp asus_wmi iTCO_wdt sparse_keymap iTCO_vendor_support lpc_ich rfkill serio_raw joydev snd_timer mfd_core i2c_i801 kvm mei_me mei snd wmi crct10dif_pclmul crc32_pclmul ghash_clmulni_intel microcode tpm_tis tpm_infineon tpm shpchp soundcore nfsd auth_rpcgss nfs_acl lockd sunrpc usb_storage hid_logitech_dj btrfs xor i915 raid6_pq i2c_algo_bit drm_kms_helper drm crc32c_intel r8169 mii i2c_core video CPU: 3 PID: 2050 Comm: kio_file Not tainted 3.14.4-200.fc20.x86_64 #1 Hardware name: System manufacturer System Product Name/P8Z77-M PRO, BIOS 2105 09/06/2013 0000000000000000 000000000ec51acf ffff8800a9171548 ffffffff816ef1d2 0000000000000000 ffff8800a9171580 ffffffff8108a1bd ffff8800a91718b0 ffff8800a917189c 0000000000000000 ffff8800cb465360 ffff8801fb6d5908 Call Trace: [<ffffffff816ef1d2>] dump_stack+0x45/0x56 [<ffffffff8108a1bd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8108a2ea>] warn_slowpath_null+0x1a/0x20 [<ffffffffa01df3f8>] cow_file_range+0x438/0x450 [btrfs] [<ffffffffa01f953f>] ? free_extent_buffer+0x4f/0xb0 [btrfs] [<ffffffffa01df7c2>] run_delalloc_nocow+0x3b2/0xa90 [btrfs] [<ffffffffa01e01a8>] run_delalloc_range+0x308/0x360 [btrfs] [<ffffffffa01f5f19>] ? find_lock_delalloc_range.constprop.44+0x1c9/0x1f0 [btrfs] [<ffffffffa01f7134>] __extent_writepage+0x314/0x790 [btrfs] [<ffffffff81174dc3>] ? find_get_pages_tag+0x103/0x1d0 [<ffffffffa01f783a>] extent_write_cache_pages.isra.30.constprop.50+0x28a/0x400 [btrfs] [<ffffffffa01f8c0c>] extent_writepages+0x5c/0x90 [btrfs] [<ffffffffa01dce20>] ? btrfs_submit_direct+0x6c0/0x6c0 [btrfs] [<ffffffffa01da808>] btrfs_writepages+0x28/0x30 [btrfs] [<ffffffff811811ae>] do_writepages+0x1e/0x40 [<ffffffff811759cd>] __filemap_fdatawrite_range+0x5d/0x80 [<ffffffff81175ab3>] filemap_fdatawrite_range+0x13/0x20 [<ffffffffa01f2339>] btrfs_wait_ordered_range+0x49/0x140 [btrfs] [<ffffffffa021a952>] __btrfs_write_out_cache+0x6a2/0x8c0 [btrfs] [<ffffffffa021aeba>] btrfs_write_out_cache+0xaa/0xe0 [btrfs] [<ffffffffa01c84f3>] btrfs_write_dirty_block_groups+0x5c3/0x6b0 [btrfs] [<ffffffffa0248931>] commit_cowonly_roots+0x15a/0x230 [btrfs] [<ffffffffa01d8610>] btrfs_commit_transaction+0x440/0x9a0 [btrfs] [<ffffffffa01a6310>] btrfs_sync_fs+0x50/0xb0 [btrfs] [<ffffffff8121a072>] sync_filesystem+0x72/0xa0 [<ffffffff811eba50>] generic_shutdown_super+0x30/0xf0 [<ffffffff811ebcd2>] kill_anon_super+0x12/0x20 [<ffffffffa01a8e86>] btrfs_kill_super+0x16/0x90 [btrfs] [<ffffffff811ec06d>] deactivate_locked_super+0x3d/0x60 [<ffffffff811ec636>] deactivate_super+0x46/0x60 [<ffffffff81208dac>] mntput_no_expire+0xac/0x140 [<ffffffff81208e64>] mntput+0x24/0x40 [<ffffffff811eb46a>] __fput+0x16a/0x230 [<ffffffff811eb57e>] ____fput+0xe/0x10 [<ffffffff810aafd7>] task_work_run+0xa7/0xe0 [<ffffffff81014ac1>] do_notify_resume+0x61/0xa0 [<ffffffff816ff822>] int_signal+0x12/0x17
Created attachment 898641 [details] File: dmesg
*********** 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.