?So I'm having a lot of problems with unraid 6.1.9 (and 6.1.7 as well) where I'm getting kernel panics.  So far I have not been able to catch the information, and the console is dead, so I can't see the top of the stack trace, and the part on the screen is uninteresting.  So I started forcing the syslog to the flash unbuffered to try and catch it, and I started getting the trace below over and over and over (multiple times per second - the syslog is 130 MB from just a few hours).  THe only difference is that sometimes it says "nzbget Tainted" and sometimes it says "nzbget Not Tainted".  Since it was a btrfs function I did a scrub, and got no errors.  I'm running 6 dockers in a 20 GB image (nzbget, delugevpn, sonarr, plex media server, couchpotato and crashplan) most are binhex dockers (Plex is needo).  At some point after this started, one of my disks was taken offline (according to the notifications by a read error). Not sure there's any relationship between these two events.

 

Any thoughts?

========================================================

 

Mar 21 19:37:44 QNas kernel: ------------[ cut here ]------------

Mar 21 19:37:44 QNas kernel: WARNING: CPU: 0 PID: 23502 at mm/truncate.c:365 truncate_inode_pages_range+0x467/0x4fd()

Mar 21 19:37:44 QNas kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_amd kvm vhost_net vhost macvtap macvlan tun 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 fam15h_power mvsas k10temp libsas scsi_transport_sas i2c_piix4 pl2303 e1000e ptp ahci usbserial libahci pps_core acpi_cpufreq

Mar 21 19:37:44 QNas kernel: CPU: 0 PID: 23502 Comm: nzbget Tainted: G        W      4.1.18-unRAID #1

Mar 21 19:37:44 QNas kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./F2A88XM-D3H, BIOS F8 04/09/2015

Mar 21 19:37:44 QNas kernel: 0000000000000009 ffff880026857b88 ffffffff815f2403 ffffffff8182e140

Mar 21 19:37:44 QNas kernel: 0000000000000292 000000000000016d 0000000000000000 ffff880026857bc8

Mar 21 19:37:44 QNas kernel: ffffffff8104778b ffffffffffffffff ffffffff810bd3f9 ffff8801deb7ced0

Mar 21 19:37:44 QNas kernel: Call Trace:

Mar 21 19:37:44 QNas kernel: [<ffffffff815f2403>] dump_stack+0x65/0x85

Mar 21 19:37:44 QNas kernel: [<ffffffff8104778b>] warn_slowpath_common+0x97/0xb1

Mar 21 19:37:44 QNas kernel: [<ffffffff810bd3f9>] ? truncate_inode_pages_range+0x467/0x4fd

Mar 21 19:37:44 QNas kernel: [<ffffffff81047839>] warn_slowpath_null+0x15/0x17

Mar 21 19:37:44 QNas kernel: [<ffffffff810bd3f9>] truncate_inode_pages_range+0x467/0x4fd

Mar 21 19:37:44 QNas kernel: [<ffffffff810bd49c>] truncate_inode_pages+0xd/0xf

Mar 21 19:37:44 QNas kernel: [<ffffffff810bd4d5>] truncate_inode_pages_final+0x37/0x3c

Mar 21 19:37:44 QNas kernel: [<ffffffff812b6b1e>] btrfs_evict_inode+0x5d/0x47b

Mar 21 19:37:44 QNas kernel: [<ffffffff81112526>] evict+0xa8/0x150

Mar 21 19:37:44 QNas kernel: [<ffffffff8111300b>] iput+0x15d/0x166

Mar 21 19:37:44 QNas kernel: [<ffffffff8110a11e>] do_unlinkat+0x136/0x24c

Mar 21 19:37:44 QNas kernel: [<ffffffff810d66b6>] ? vm_munmap+0x4b/0x5b

Mar 21 19:37:44 QNas kernel: [<ffffffff8110a83c>] SyS_unlink+0x11/0x13

Mar 21 19:37:44 QNas kernel: [<ffffffff815f7b2e>] system_call_fastpath+0x12/0x71

Mar 21 19:37:44 QNas kernel: ---[ end trace 97cb983a444705db ]---

qnas-diagnostics-20160322-1032.zip

THis seems related to binhex-sonarr and binhex-delugevpn not playing well together for some reason in my setup....