From owner-freebsd-bugs@freebsd.org Fri Dec 13 11:08:48 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 76A201CA68C for ; Fri, 13 Dec 2019 11:08:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 47Z7Fr2c2yz3PTr for ; Fri, 13 Dec 2019 11:08:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 574B11CA68B; Fri, 13 Dec 2019 11:08:48 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 55F8C1CA68A for ; Fri, 13 Dec 2019 11:08:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Z7Fr1QBzz3PTq for ; Fri, 13 Dec 2019 11:08:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 27DE2B2AC for ; Fri, 13 Dec 2019 11:08:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id xBDB8m3f069016 for ; Fri, 13 Dec 2019 11:08:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xBDB8mgQ069013 for bugs@FreeBSD.org; Fri, 13 Dec 2019 11:08:48 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 242621] iscsi initiator does not provide devices after reconnection Date: Fri, 13 Dec 2019 11:08:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: info@dominicschlegel.ch X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2019 11:08:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242621 Bug ID: 242621 Summary: iscsi initiator does not provide devices after reconnection Product: Base System Version: 11.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: info@dominicschlegel.ch after a network disruption we see some servers having issues reestablishing iscsi block devices. this manifests itself with the following iscsictl -L output: Target name Target portal State iqn.2010-06.com.purestorage:flasharray.XXX 10.4.1.15:3260 Connected:=20 iqn.2010-06.com.purestorage:flasharray.XXX 10.4.1.16:3260 Connected:=20 iqn.2010-06.com.purestorage:flasharray.XXX 10.4.1.17:3260 Connected: da3= =20 iqn.2010-06.com.purestorage:flasharray.XXX 10.4.1.18:3260 Connected: da2= =20 As it can be seen iscsi initiator was able to reconnect da3 and da2. the ot= her 2 devices are missing. it is not possible to logout of these portals using command "iscsictl -R -p 10.4.1.15:3260". It is neither possible to add the = path again manually. Note: This is the same block device seen over 4 different paths. Stuck in this situation we see messages in the kernel log: Dec 13 12:01:24.567 hostname kernel: WARNING: 10.4.1.15:3260 (iqn.2010-06.com.purestorage:flasharray.XXX): no ping reply (NOP-In) after 5 seconds; reconnecting Dec 13 12:01:24.567 hostname kernel: WARNING: 10.4.1.15:3260 (iqn.2010-06.com.purestorage:flasharray.XXX): no ping reply (NOP-In) after 5 seconds; reconnecting Note: This messages only appear for one of the two defective target portals. We have the following iscsi sysctl's set: kern.iscsi.fail_on_shutdown: 1 kern.iscsi.fail_on_disconnection: 1 kern.iscsi.maxtags: 255 kern.iscsi.login_timeout: 60 kern.iscsi.iscsid_timeout: 60 kern.iscsi.ping_timeout: 5 We see this behaviour with different iscsi target vendors (Pure Storage, Ne= tApp eSeries) on multiple different FreeBSD 11.3 hosts. The only solution we have found so far is a reboot of the affected host. --=20 You are receiving this mail because: You are the assignee for the bug.=