https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990
Bug ID: 211990
Summary: iscsi fails to reconnect and does not release devices
Product: Base System
Version: 10.3-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: freebsd-bugs@FreeBSD.org
Reporter: ben.rub...@gmail.com
Hello,
I'm facing an issue where iscsictl does not want to remove devices.
Here is how I can reproduce this.
### Initiator :
# iscsictl -Aa
iscsictl then reports the 17 targets as connected, perfect.
### Target :
Let's switch down the network interface
# ifconfig mlxen1 down
### Initiator :
iscsictl reports the 17 targets as disconnected, perfect.
### Target :
Let's switch up the network interface
# ifconfig mlxen1 up
### Initiator :
iscsictl reports the 17 targets as connected, however, for 4 devices, I get the
following :
09:59:43 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): timed out
waiting for iscsid(8) for 11 seconds; reconnecting
09:59:54 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): timed out
waiting for iscsid(8) for 11 seconds; reconnecting
09:59:57 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): handoff on
already connected session
07:59:57 srv1 iscsid[1372]: 192.168.2.2 (iqn.2012-06.srv2:lg2): ISCSIDHANDOFF:
Device busy
09:59:57 srv1 iscsid[581]: child process 1372 terminated with exit status 1
09:59:57 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): connection
error; reconnecting
09:59:57 srv1 kernel: (da21:iscsi8:0:0:0): got CAM status 0x8
09:59:57 srv1 kernel: (da21:iscsi8:0:0:0): fatal error, failed to attach to
device
10:00:07 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): no ping
reply (NOP-In) after 10 seconds; reconnecting
10:00:08 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): no ping
reply (NOP-In) after 10 seconds; reconnecting
### Target :
09:58:50 srv2 kernel: mlxen1: link state changed to DOWN
09:58:50 srv2 kernel: mlx4_en: mlxen1: Link Down
09:58:53 srv2 kernel: WARNING: 192.168.2.1 (iqn.1994-09.org.freebsd:srv1): no
ping reply (NOP-Out) after 5 seconds; dropping connection
09:58:53 srv2 last message repeated 16 times
09:59:49 srv2 kernel: mlx4_en: mlxen1: Link Up
09:59:49 srv2 kernel: mlxen1: link state changed to UP
09:59:49 srv2 devd: Executing '/etc/rc.d/dhclient quietstart mlxen1'
09:59:59 srv2 kernel: WARNING: 192.168.2.1 (iqn.1994-09.org.freebsd:srv1):
connection error; dropping connection
09:59:59 srv2 last message repeated 3 times
### Initiator :
# iscsictl -Ra
# iscsictl -L
Target name Target portal State
iqn.2012-06.srv2:sW1 192.168.2.2 Connected: da18
iqn.2012-06.srv2:sW2 192.168.2.2 Connected: da23
iqn.2012-06.srv2:rT3 192.168.2.2 Connected: da17
iqn.2012-06.srv2:lg2 192.168.2.2 Connected: da21
As you can see, the 4 problematic devices remain "connected", nodes exist in
/dev/, but they are unusable.
Each time I "iscsictl -Ra", I get the following on initiator side :
10:09:35 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): connection
error; reconnecting
10:09:35 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:sW1): connection
error; reconnecting
10:09:35 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:rT3): connection
error; reconnecting
10:09:35 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:sW2): connection
error; reconnecting
No logs however on target side, even if I start ctld with -d.
The only workaround I found is to reboot, or to change the target name to
properly reconnect...
# uname -v
FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 18:38:15 UTC 2016
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
Thank you for your support,
Best regards,
Ben
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
