Hi,
Edward Tomasz Napierała wrote 2017-09-22 12:15:
There are two weird things here. First is that the error is coming
from
ctld(8) - the userspace daemon, not the kernel. The second is that
those
invalid opcodes are actually both valid - they are the Text Request,
and the Logout Request with Immediate flag set, exectly what you'd
expect
for a discovery session.
Do you have a way to do a packet dump?
Sure. Here it is:
http://enaza.ru/stub-data/iscsi-protocol-error.pcap
Target IP is 10.0.2.4, initiator IP is 10.0.3.127. During the session
captured in this file I got in messages:
Sep 22 15:38:11 san1 ctld[61373]: 10.0.3.127
(iqn.1991-05.com.microsoft:worker296): protocol error: received invalid
opcode 0x4
Sep 22 15:38:11 san1 ctld[61374]: 10.0.3.127
(iqn.1991-05.com.microsoft:worker296): protocol error: received invalid
opcode 0x46
This error happens when the initiator is trying to connect the disk from
a target discovered.
Target is running FreeBSD 11.0-STABLE #1 r310734M where M is for
CTL_MAX_PORTS 1024 (old verion, yup, but I have a suspicion that I still
failed to prove that more recent version have some iSCSI vs ZFS
conflict, but that's another story). Initiator is running Windows 7
Professional x64, inside a ESX virtual machine. This happens only when
some unclear threshold is crossed, previous ~2 hundreds of initiators
run Windows 7 Professional too.
If you need any additional data/diagnostics please let me know.
Eugene.
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
