Date: Sat, 18 Nov 2017 05:42:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 223381] mpt driver hangs with iscsi devices and scsi drives defined in VBOX FBSD guest Message-ID: <bug-223381-5312-hZMQ5mOlX1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-223381-5312@https.bugs.freebsd.org/bugzilla/> References: <bug-223381-5312@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223381 --- Comment #3 from Jim D. <randomnoise058@gmail.com> --- Update on situation (11/17/2017, 11:20pm CST) 1) created VirtualBox (VBox) SCSI controller and added VBox 3GB drive to it 2) modified FBSD-11.1 "fstab" to mount SCSI drive at boot (/SCSIhdd) 3) created shell script to run through a series of system commands on 3 iSCSI drives, 1 zfs drive, 1 SCSI drive every 10 minutes; FBSD11 Zabbix client not running a) dd (15 times,count=1), fsck -Cn, zpool status b) tail /var/log/messages 4) no notable issues for several hours 5) started FBSD11 Zabbix cilent with Zabbix server active but Zabbix queries disabled 6) no notable issues 7) modified Zabbix configuration for FBSD11 client a) removed Zabbix FreeBSD template which included various file system checks b) left special locally developed template to perform HDD discovery, status check, and other miscellaneous HDD information reporting 8) activated Zabbix server queries to FBSD11 client 9) script above continues to run without any notable issues 10) after some time, kernel WARNING messages related to iSCSI appeared kernel: WARNING: 192.168.1.19:3260 (iqn.2000-01.com.synology:ds216j.Target-7.c16e0895b7): underflow mismatch: target indicates 0, we calculated 4 11) stopped Zabbix server queries 12) modified special local Zabbix template to exclude extensive HDD status testing (ls, dd, mount, fsck, smartctl, ZFS pool status, iSCSI Target status) 13) reconfigured Zabbix definition for FBSD11 client to use modified template 14) re-started Zabbix server queries to FBSD11 client; above script still running 15) after 1.5 hours, no iSCSI related kernel WARNING messages have appeared Initial conclusion: something within the extensive HDD status testing is probably causing whatever to occur which results in the kernel WARNING messages. It may, or may not, be the iSCSI Target query using "iscsictl". More testing is required to further nail done the specific command(s) related to the iSCSI issue which as reported earlier which would eventually cause the FBSD11 client host to hang. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-223381-5312-hZMQ5mOlX1>