Date: Fri, 13 Dec 2019 11:08:47 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 242621] iscsi initiator does not provide devices after reconnection Message-ID: <bug-242621-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242621 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: iqn.2010-06.com.purestorage:flasharray.XXX 10.4.1.16:3260 Connected: iqn.2010-06.com.purestorage:flasharray.XXX 10.4.1.17:3260 Connected: da3 iqn.2010-06.com.purestorage:flasharray.XXX 10.4.1.18:3260 Connected: da2 As it can be seen iscsi initiator was able to reconnect da3 and da2. the other 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, NetApp eSeries) on multiple different FreeBSD 11.3 hosts. The only solution we have found so far is a reboot of the affected host. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242621-227>