From owner-freebsd-scsi@freebsd.org Sun Oct 29 15:30:00 2017 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9F1CE42564 for ; Sun, 29 Oct 2017 15:30:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A764381864 for ; Sun, 29 Oct 2017 15:30:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9TFU0aD090993 for ; Sun, 29 Oct 2017 15:30:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 223238] Persistent iscsi underflow mismatch errors followed by apparent kernel panic Date: Sun, 29 Oct 2017 15:30:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: randomnoise058@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2017 15:30:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223238 --- Comment #7 from Jim D. --- On the target side, I know that the Synology SAN/NAS has some disk monitori= ng. There are scheduled smart tests, but they are weeks to months apart. All Synology administrative console smartctl resuls show "Normal" for the affec= ted target HDD. There are also several Synology applications running related to "cloud services" (thumbd,syncd,cloud-cleand,storaged). There is also an ecryptfs-kthread task and a synoindexd task. There have been a couple of Synology SAN/NAS firwmware updates over the past month or so. On the initiator side - I am occassionally running Zabbix to query hard dri= ves (client script: ls,dd,fsck,fdisk,iostat,smartctl,diskutil,system_profiler) every 10-15 minutes. On some targets I also run ZFS queries and iSCSI (lsscsi,iscsiadm,iscsictl) queries. But nothing that does presistent monito= ring (like every few seconds or non-stop). I have at times 8-10 client hosts (physical and virtual) monitored by either a physical Zabbix or a virtual Zabbix, all of which have iSCSI targets.Right now I have 12 targets with 19 LUNs defined attached to 6 different *nix OS's/versions. I am unable to see any more screen output when the FBSD VirtualBox machine locks up. Neither the VBox console nor the SSH terminal are responsive. I m= ight be able to run a trace to a file, but don't know if that will capture what = you are interested in - the data might never get written to local (VBox) disk e= ven if there was something worth seeing. When I look at locked-up-client-host messages, there is nothing but "last timed entry" and the next startup entr= y. I have enabled the /etc/syslog.conf configuration for the "console log". Perhaps that will capture some additional information. Past experience has shown, however, that open log files during a system crash/lock up may not receive all of the possible data in the log file. --=20 You are receiving this mail because: You are the assignee for the bug.=