MisterWolfe Posted March 13, 2017 Share Posted March 13, 2017 I've gotten a warning about Call traces in my syslog from the Fix Common problems plugin. It looks like a kernel issue, but I'm not sure what, if anything, I can do to solve it. Any input would be appreciated. I've attached the diagnostics file, and included the call trace inside the post. Thank you! Mar 13 10:04:11 Tower kernel: ------------[ cut here ]------------ Mar 13 10:04:11 Tower kernel: WARNING: CPU: 2 PID: 13689 at fs/btrfs/extent-tree.c:134 btrfs_put_block_group+0x42/0x59 Mar 13 10:04:11 Tower kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod hwmon_vid pata_marvell coretemp kvm_intel kvm r8169 mii ahci libahci sata_mv i2c_i801 intel_agp i2c_smbus intel_gtt i2c_core ata_piix agpgart asus_atk0110 acpi_cpufreq [last unloaded: md_mod] Mar 13 10:04:11 Tower kernel: CPU: 2 PID: 13689 Comm: umount Not tainted 4.9.10-unRAID #1 Mar 13 10:04:11 Tower kernel: Hardware name: System manufacturer System Product Name/P5Q-PRO, BIOS 2102 02/23/2009 Mar 13 10:04:11 Tower kernel: ffffc900053ebd20 ffffffff813a353e 0000000000000000 ffffffff81968f2d Mar 13 10:04:11 Tower kernel: ffffc900053ebd60 ffffffff8104d00c 00000086053ebd00 ffff880222bb3c00 Mar 13 10:04:11 Tower kernel: ffff880222bb3ce8 ffff880222476090 ffff880222bb3c00 ffff8802224760a0 Mar 13 10:04:11 Tower kernel: Call Trace: Mar 13 10:04:11 Tower kernel: [<ffffffff813a353e>] dump_stack+0x61/0x7e Mar 13 10:04:11 Tower kernel: [<ffffffff8104d00c>] __warn+0xb8/0xd3 Mar 13 10:04:11 Tower kernel: [<ffffffff8104d0d4>] warn_slowpath_null+0x18/0x1a Mar 13 10:04:11 Tower kernel: [<ffffffff812d591a>] btrfs_put_block_group+0x42/0x59 Mar 13 10:04:11 Tower kernel: [<ffffffff812dbc2b>] btrfs_free_block_groups+0x19d/0x39b Mar 13 10:04:11 Tower kernel: [<ffffffff812eadf9>] close_ctree+0x1d4/0x2e8 Mar 13 10:04:11 Tower kernel: [<ffffffff81137d51>] ? evict_inodes+0x128/0x137 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5c50>] btrfs_put_super+0x14/0x16 Mar 13 10:04:11 Tower kernel: [<ffffffff8112305b>] generic_shutdown_super+0x6a/0xeb Mar 13 10:04:11 Tower kernel: [<ffffffff811232be>] kill_anon_super+0xd/0x17 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5b97>] btrfs_kill_super+0x11/0x94 Mar 13 10:04:11 Tower kernel: [<ffffffff811234b0>] deactivate_locked_super+0x3b/0x68 Mar 13 10:04:11 Tower kernel: [<ffffffff81123e34>] deactivate_super+0x39/0x3c Mar 13 10:04:11 Tower kernel: [<ffffffff8113acd2>] cleanup_mnt+0x53/0x71 Mar 13 10:04:11 Tower kernel: [<ffffffff8113ad24>] __cleanup_mnt+0xd/0xf Mar 13 10:04:11 Tower kernel: [<ffffffff81062530>] task_work_run+0x6a/0x7d Mar 13 10:04:11 Tower kernel: [<ffffffff81002b24>] exit_to_usermode_loop+0x55/0x81 Mar 13 10:04:11 Tower kernel: [<ffffffff81002c61>] syscall_return_slowpath+0x44/0x47 Mar 13 10:04:11 Tower kernel: [<ffffffff8167d344>] entry_SYSCALL_64_fastpath+0xa7/0xa9 Mar 13 10:04:11 Tower kernel: ---[ end trace 8e45affbece91bb7 ]--- Mar 13 10:04:11 Tower kernel: ------------[ cut here ]------------ Mar 13 10:04:11 Tower kernel: WARNING: CPU: 2 PID: 13689 at fs/btrfs/extent-tree.c:10045 btrfs_free_block_groups+0x37a/0x39b Mar 13 10:04:11 Tower kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod hwmon_vid pata_marvell coretemp kvm_intel kvm r8169 mii ahci libahci sata_mv i2c_i801 intel_agp i2c_smbus intel_gtt i2c_core ata_piix agpgart asus_atk0110 acpi_cpufreq [last unloaded: md_mod] Mar 13 10:04:11 Tower kernel: CPU: 2 PID: 13689 Comm: umount Tainted: G W 4.9.10-unRAID #1 Mar 13 10:04:11 Tower kernel: Hardware name: System manufacturer System Product Name/P5Q-PRO, BIOS 2102 02/23/2009 Mar 13 10:04:11 Tower kernel: ffffc900053ebd38 ffffffff813a353e 0000000000000000 ffffffff81968f2d Mar 13 10:04:11 Tower kernel: ffffc900053ebd78 ffffffff8104d00c 0000273d053ebd40 ffff880222476000 Mar 13 10:04:11 Tower kernel: ffff880221e1bc88 ffff880221e1bc00 ffff880222476b30 0000000000000000 Mar 13 10:04:11 Tower kernel: Call Trace: Mar 13 10:04:11 Tower kernel: [<ffffffff813a353e>] dump_stack+0x61/0x7e Mar 13 10:04:11 Tower kernel: [<ffffffff8104d00c>] __warn+0xb8/0xd3 Mar 13 10:04:11 Tower kernel: [<ffffffff8104d0d4>] warn_slowpath_null+0x18/0x1a Mar 13 10:04:11 Tower kernel: [<ffffffff812dbe08>] btrfs_free_block_groups+0x37a/0x39b Mar 13 10:04:11 Tower kernel: [<ffffffff812eadf9>] close_ctree+0x1d4/0x2e8 Mar 13 10:04:11 Tower kernel: [<ffffffff81137d51>] ? evict_inodes+0x128/0x137 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5c50>] btrfs_put_super+0x14/0x16 Mar 13 10:04:11 Tower kernel: [<ffffffff8112305b>] generic_shutdown_super+0x6a/0xeb Mar 13 10:04:11 Tower kernel: [<ffffffff811232be>] kill_anon_super+0xd/0x17 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5b97>] btrfs_kill_super+0x11/0x94 Mar 13 10:04:11 Tower kernel: [<ffffffff811234b0>] deactivate_locked_super+0x3b/0x68 Mar 13 10:04:11 Tower kernel: [<ffffffff81123e34>] deactivate_super+0x39/0x3c Mar 13 10:04:11 Tower kernel: [<ffffffff8113acd2>] cleanup_mnt+0x53/0x71 Mar 13 10:04:11 Tower kernel: [<ffffffff8113ad24>] __cleanup_mnt+0xd/0xf Mar 13 10:04:11 Tower kernel: [<ffffffff81062530>] task_work_run+0x6a/0x7d Mar 13 10:04:11 Tower kernel: [<ffffffff81002b24>] exit_to_usermode_loop+0x55/0x81 Mar 13 10:04:11 Tower kernel: [<ffffffff81002c61>] syscall_return_slowpath+0x44/0x47 Mar 13 10:04:11 Tower kernel: [<ffffffff8167d344>] entry_SYSCALL_64_fastpath+0xa7/0xa9 Mar 13 10:04:11 Tower kernel: ---[ end trace 8e45affbece91bb8 ]--- Mar 13 10:04:11 Tower kernel: BTRFS info (device loop0): space_info 4 has 993476608 free, is not full Mar 13 10:04:11 Tower kernel: BTRFS info (device loop0): space_info total=1342177280, used=348618752, pinned=0, reserved=16384, may_use=0, readonly=65536 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524769280 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524773376 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524777472 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524781568 tower-diagnostics-20170313-1030.zip Quote Link to comment
Squid Posted March 13, 2017 Share Posted March 13, 2017 Those errors are from the docker.img file. However, the ultimate cause is that there are problems with the file system on the cache drive Mar 13 02:05:11 Tower kernel: XFS (sdd1): Metadata corruption detected at xfs_inode_buf_verify+0x92/0xb8, xfs_inode block 0xf17b110 Mar 13 02:05:11 Tower kernel: XFS (sdd1): Metadata corruption detected at xfs_inode_buf_verify+0x92/0xb8, xfs_inode block 0xf17b110 You need to Check Disk Filesystems on the cache drive. If you still have issues, then you will also need to toast and recreate the docker.img file -> All your apps will be unaffected Delete the docker.img file (Settings -> Docker -> Stop the service -> delete the docker.img file -> Renable) Followed by 1 Quote Link to comment
MisterWolfe Posted March 13, 2017 Author Share Posted March 13, 2017 Thanks, Squid! I appreciate the assistance. I'll start a file system check and go from there. Quote Link to comment
MisterWolfe Posted March 13, 2017 Author Share Posted March 13, 2017 Repairing the file system on the cache drive was the solution. Thanks again! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.