Date: Mon, 2 Oct 2017 11:03:39 +0100 From: Edward Napierala <trasz@freebsd.org> To: "Eugene M. Zheganin" <emz@norma.perm.ru> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: ctld: only 579 iSCSI targets can be created Message-ID: <CAFLM3-pKB9LfJQRXOb0EKtqYzN1CfYX8HUZqX2Z6zDe8DqTspw@mail.gmail.com> In-Reply-To: <739fe048ccbe15c096ec79fc320eee56@norman-vivat.ru> References: <04e8820c2c6cc7a95d6ffdf257f00f7d@norman-vivat.ru> <20170922071554.GA3846@brick> <739fe048ccbe15c096ec79fc320eee56@norman-vivat.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the packet trace. What happens there is that the Windows
initiator logs in, requests Discovery ("SendTargets=3DAll"), receives the l=
ist
of targets, as expected, and then... sends "SendTargets=3DAll" again,
instead of logging off. This results in ctld(8) dropping the session.
The initiator then starts the Discovery session again, but this time it onl=
y
logs in and then out, without actually requesting the target list.
Perhaps you could work around this by using "discovery-filter",
as documented in ctl.conf(5)?
2017-09-22 11:49 GMT+01:00 Eugene M. Zheganin <emz@norma.perm.ru>:
> Hi,
>
> Edward Tomasz Napiera=C5=82a 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 thos=
e
>> invalid opcodes are actually both valid - they are the Text Request,
>> and the Logout Request with Immediate flag set, exectly what you'd expec=
t
>> 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:w=
orker296):
> protocol error: received invalid opcode 0x4
> Sep 22 15:38:11 san1 ctld[61374]: 10.0.3.127 (iqn.1991-05.com.microsoft:w=
orker296):
> 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 x6=
4,
> inside a ESX virtual machine. This happens only when some unclear thresho=
ld
> is crossed, previous ~2 hundreds of initiators run Windows 7 Professional
> too.
>
> If you need any additional data/diagnostics please let me know.
>
> Eugene.
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFLM3-pKB9LfJQRXOb0EKtqYzN1CfYX8HUZqX2Z6zDe8DqTspw>