From owner-freebsd-hackers@freebsd.org  Tue Nov 14 09:09:08 2017
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@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 10167DB897E;
 Tue, 14 Nov 2017 09:09:08 +0000 (UTC)
 (envelope-from danny@cs.huji.ac.il)
Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C05137618F;
 Tue, 14 Nov 2017 09:09:07 +0000 (UTC)
 (envelope-from danny@cs.huji.ac.il)
Received: from bach.cs.huji.ac.il ([132.65.80.20])
 by kabab.cs.huji.ac.il with esmtp
 id 1eEXDD-000O9b-U4; Tue, 14 Nov 2017 11:08:55 +0200
From: Daniel Braniss <danny@cs.huji.ac.il>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: iscsi target and VMware/esxi timeouts
Message-Id: <7779629C-A1E5-4E96-B660-A0FAD231468C@cs.huji.ac.il>
Date: Tue, 14 Nov 2017 11:08:55 +0200
Cc: stable@freebsd.org
To: Freebsd hackers list <freebsd-hackers@freebsd.org>,
 =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= <trasz@FreeBSD.org>
X-Mailer: Apple Mail (2.3445.4.7)
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Nov 2017 09:09:08 -0000

Hi,
we are experimenting issues with several esxi=E2=80=99s servers that use =
freebsd 10.2 stable as a iscsi target.
ie:
Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.201 =
(iqn.1998-01.com.vmware:pe-02-2fa7cd9e): no ping reply (NOP-Out) after 5 =
seconds; dropping connection
Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.201 =
(iqn.1998-01.com.vmware:pe-02-2fa7cd9e): no ping reply (NOP-Out) after 5 =
seconds; dropping connection
Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.205 =
(iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 =
seconds; dropping connection
Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.203 =
(iqn.1998-01.com.vmware:pe-13-60e87d06): no ping reply (NOP-Out) after 5 =
seconds; dropping connection
Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.205 =
(iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 =
seconds; dropping connection

these are 3 different esxis that almost at the same time the target =
looses connection to the initiators.
at the moment most =E2=80=98clients=E2=80=99  recover from the scsi =
error, but older freebsds don=E2=80=99t.

in any case, increasing the timeout is not helping.

any clues are welcome :-)

over the weekend i=E2=80=99m planning to upgrade the target to 11.1 and =
take for the hills.

danny