Hide Forgot
Description of problem: One file that was being written during a power failure, appeared after reboot as: [backup@xenon repo]$ ls -la data/0/3833 ?---------. 1 root root 0 ene 1 1970 data/0/3833 I decided to delete it, but I got this bug after a few seconds Additional info: reporter: libreport-2.8.0 kernel BUG at fs/btrfs/delayed-inode.c:1561! invalid opcode: 0000 [#1] SMP Modules linked in: xfs libcrc32c rfcomm fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun xt_set xt_multiport ip_set_hash_ip nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_tftp ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_conntrack ip_set nfnetlink ebtable_broute bridge ebtable_nat ip6table_security ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle iptable_security iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep vfat fat eeepc_wmi asus_wmi iTCO_wdt iTCO_vendor_support sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel btrfs kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel intel_cstate intel_uncore xor snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi intel_rapl_perf snd_hda_intel snd_hda_codec uvcvideo snd_usb_audio snd_hda_core snd_usbmidi_lib snd_rawmidi btusb snd_hwdep i2c_i801 snd_seq btrtl videobuf2_vmalloc btbcm btintel raid6_pq videobuf2_memops snd_seq_device videobuf2_v4l2 bluetooth i2c_smbus snd_pcm videobuf2_core videodev snd_timer snd mei_me joydev rfkill media mei soundcore lpc_ich shpchp wmi tpm_tis video tpm_tis_core tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc amdkfd amd_iommu_v2 radeon i2c_algo_bit drm_kms_helper 8021q garp ttm stp llc mrp crc32c_intel drm r8169 serio_raw uas mii usb_storage fjes CPU: 0 PID: 10691 Comm: rm Not tainted 4.8.6-300.fc25.x86_64 #1 Hardware name: System manufacturer System Product Name/P8Z68-V LE, BIOS 4102 09/09/2013 task: ffff94ccac7a3d00 task.stack: ffff94cc0bf14000 RIP: 0010:[<ffffffffc0d80a92>] [<ffffffffc0d80a92>] btrfs_delete_delayed_dir_index+0x222/0x2c0 [btrfs] RSP: 0018:ffff94cc0bf17d18 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff94ccba0dbdb0 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff94cd1ec0e048 RDI: ffff94cd1ec0e048 RBP: ffff94cc0bf17d88 R08: 0000000000098b7f R09: 0000000000000005 R10: ffff94cd0703c400 R11: 0000000000000483 R12: ffff94ccba0dbdf8 R13: ffff94cd071b2800 R14: 0000000000000032 R15: 0000000000000000 FS: 00007fb8228b5700(0000) GS:ffff94cd1ec00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f512fa32000 CR3: 000000030bd31000 CR4: 00000000000406f0 Stack: ffff94cd0ac81a20 ffff94cc0bf17d58 0000000000040000 ffff94cd0703c400 ffff94cd0703c400 0900000000000000 6000000000000001 0000000000000032 000000006dbfa5b9 ffff94cc4266da88 ffff94cc6c073d00 0000000000003272 Call Trace: [<ffffffffc0d28db1>] __btrfs_unlink_inode+0x1b1/0x4b0 [btrfs] [<ffffffffc0d2ca1c>] btrfs_unlink_inode+0x1c/0x40 [btrfs] [<ffffffffc0d2caab>] btrfs_unlink+0x6b/0xc0 [btrfs] [<ffffffff8725d188>] vfs_unlink+0x108/0x190 [<ffffffff872618b7>] do_unlinkat+0x277/0x2f0 [<ffffffff872623fb>] SyS_unlinkat+0x1b/0x30 [<ffffffff87802572>] entry_SYSCALL_64_fastpath+0x1a/0xa4 Code: eb fe ff ff 48 8b 53 10 49 8b bd f0 01 00 00 41 89 c1 4c 8b 03 48 c7 c6 d0 1b db c0 48 8b 8a 48 03 00 00 4c 89 f2 e8 fe f5 f6 ff <0f> 0b 65 8b 05 8d 96 28 3f 89 c0 48 0f a3 05 db 5b 1d c7 73 b7 RIP [<ffffffffc0d80a92>] btrfs_delete_delayed_dir_index+0x222/0x2c0 [btrfs] RSP <ffff94cc0bf17d18>
Created attachment 1218174 [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 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. 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 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 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.
Sorry, I can't reproduce this bug, don't know if it's still present.