From owner-freebsd-scsi@freebsd.org  Wed Nov  1 09:12:06 2017
Return-Path: <owner-freebsd-scsi@freebsd.org>
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 003ABE4FDF6
 for <freebsd-scsi@mailman.ysv.freebsd.org>;
 Wed,  1 Nov 2017 09:12:06 +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 E2D0163FF2
 for <freebsd-scsi@FreeBSD.org>; Wed,  1 Nov 2017 09:12:05 +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 vA19C59B096762
 for <freebsd-scsi@FreeBSD.org>; Wed, 1 Nov 2017 09:12:05 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: Wed, 01 Nov 2017 09:12:05 +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: <bug-223238-5312-a6eX1cABDa@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-223238-5312@https.bugs.freebsd.org/bugzilla/>
References: <bug-223238-5312@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-scsi.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi/>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Nov 2017 09:12:06 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223238

--- Comment #16 from Jim D. <randomnoise058@gmail.com> ---
Deleted the VBOX FBSD SCSI drives and controller. Can't change drive type o=
nce
defined. Not a problem as they were dummy drives just to test VBOX SCSI
alongside iSCSI.

Deleted ZFS pool, which used one of the VBOX SCSI drives, and recreated it
using repurposed SATA VBOX drive.

Synology/iSCSI WARNING messages still flow but the VBOX FBSD guest has been
stable for 9 hours now. Lots of Zabbix queries flow to and from the VBOX FB=
SD
guest without any hiccups.

FWIW - the VBOX SCSI controller is based on either an LSIlogic or BUSlogic
driver.

I will leave everything running for awhile longer.

--=20
You are receiving this mail because:
You are the assignee for the bug.=