wgstarks Posted February 5, 2017 Share Posted February 5, 2017 After some problems yesterday I'm now getting a report from FCP regarding call trace errors. Not sure if the problems are related so I started a separate thread for this. Diagnostics attached. brunnhilde-diagnostics-20170205-0850.zip Link to comment
Squid Posted February 5, 2017 Share Posted February 5, 2017 Feb 4 18:17:25 Brunnhilde kernel: WARNING: CPU: 0 PID: 2431 at fs/btrfs/extent-tree.c:138 btrfs_put_block_group+0x44/0x5c() Feb 4 18:17:25 Brunnhilde kernel: Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod ipmi_devintf ahci igb i2c_i801 e1000e libahci i2c_algo_bit ptp pps_core mpt2sas raid_class scsi_transport_sas ipmi_si [last unloaded: md_mod] Feb 4 18:17:25 Brunnhilde kernel: CPU: 0 PID: 2431 Comm: umount Not tainted 4.1.18-unRAID #1 Feb 4 18:17:25 Brunnhilde kernel: Hardware name: Supermicro X10SLL-F/X10SLL-F, BIOS 3.0a 12/21/2015 Feb 4 18:17:25 Brunnhilde kernel: 0000000000000009 ffff880372fd3ce8 ffffffff815f2403 ffffffff8182e140 Feb 4 18:17:25 Brunnhilde kernel: 0000000000000292 000000000000008a 0000000000000000 ffff880372fd3d28 Feb 4 18:17:25 Brunnhilde kernel: ffffffff8104778b ffff880372fd3d28 ffffffff81295b60 ffff880409ea7200 Feb 4 18:17:25 Brunnhilde kernel: Call Trace: Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff815f2403>] dump_stack+0x65/0x85 Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff8104778b>] warn_slowpath_common+0x97/0xb1 Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff81295b60>] ? btrfs_put_block_group+0x44/0x5c Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff81047839>] warn_slowpath_null+0x15/0x17 Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff81295b60>] btrfs_put_block_group+0x44/0x5c Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff8129de19>] btrfs_free_block_groups+0x193/0x391 Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff812a9670>] close_ctree+0x1d1/0x2e3 Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff81113543>] ? evict_inodes+0xef/0xfe Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff81286020>] btrfs_put_super+0x14/0x16 Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff810ff287>] generic_shutdown_super+0x6e/0xea Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff810ff4ef>] kill_anon_super+0xe/0x19 Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff81285dfc>] btrfs_kill_super+0x13/0x8f Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff810ff7e3>] deactivate_locked_super+0x3b/0x68 Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff810ffcca>] deactivate_super+0x3a/0x3e Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff81115e33>] cleanup_mnt+0x54/0x73 Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff81115e88>] __cleanup_mnt+0xd/0xf Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff8105b571>] task_work_run+0x93/0xae Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff8100b39e>] do_notify_resume+0x40/0x4e Feb 4 18:17:25 Brunnhilde kernel: [<ffffffff815f7cfc>] int_signal+0x12/0x17 Feb 4 18:17:25 Brunnhilde kernel: ---[ end trace 853a1b22af97ceb4 ]--- Feb 4 18:17:25 Brunnhilde kernel: BTRFS warning (device loop0): page private not zero on page 509624320 Feb 4 18:17:25 Brunnhilde kernel: BTRFS warning (device loop0): page private not zero on page 509628416 Feb 4 18:17:25 Brunnhilde kernel: BTRFS warning (device loop0): page private not zero on page 509632512 Feb 4 18:17:25 Brunnhilde kernel: BTRFS warning (device loop0): page private not zero on page 509636608 Looks like BTRFS is having a hissy-fit on your docker.img file I don't see any issues with the cache drive itself, so probably the docker.img is just plain corrupted (filled up?) Easiest solution is to delete the docker.img, recreate it and then add the apps back in either using the my* templates from the add container screen or in CA and the Previous Apps section. Either way the templates will be already prefilled out and after the downloads everything should be back to normal without any adjustments of the templates. Link to comment
wgstarks Posted February 5, 2017 Author Share Posted February 5, 2017 Which docker image? I have the ls-io PMS docker and plexreport. Link to comment
Squid Posted February 5, 2017 Share Posted February 5, 2017 Which docker image? I have the ls-io PMS docker and plexreport. The docker.img file itself Settings - Docker - Stop - Delete Link to comment
wgstarks Posted February 5, 2017 Author Share Posted February 5, 2017 Ok thanks. Will FCP continue to report the call trace error from that log entry? Wondering if I should also reboot to clear the log file? Link to comment
Squid Posted February 5, 2017 Share Posted February 5, 2017 Ok thanks. Will FCP continue to report the call trace error from that log entry? Wondering if I should also reboot to clear the log file? If you acknowledge it, it will ignore all call traces until the next reboot... If you don't acknowledge, then it will continue to warn you every time it runs... A reboot is probably the best... Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.