Hello,
when our ESXi hosts (re)connect to an iSCSI target, I sometimes see
the following errors in dmesg:
[248476.396730] sock_ops->getname() failed.
[248476.396734] tx_data returned less than expected
[248476.396735] iSCSI Login negotiation failed.
[248476.396782] tx_data returned -32, expecting 112.
[248476.396785] iSCSI Login negotiation failed.
[248476.396802] sock_ops->getname() failed.
[248476.396805] tx_data returned less than expected
[248476.396806] iSCSI Login negotiation failed.
[248476.396811] sock_ops->getname() failed.
[248476.396813] tx_data returned less than expected
[248476.396814] iSCSI Login negotiation failed.
[249424.088714] tx_data returned -32, expecting 112.
[249424.088717] iSCSI Login negotiation failed.
[249424.339221] rx_data returned 0, expecting 48.
[249424.339224] iSCSI Login negotiation failed.
It usually happens when I disable and remove the target setup from
/sys/kernel/config and then configure+enable it again few seconds
later. That is, when vSphere hosts are intensively trying to establish
new sessions. Is it something I should worry about? ESXi quickly
repeats login attempts until it succeeds so there is no long downtime,
but the errors look strange (negative tx_data, sock_ops->getname()
failure?).
(Seen in v3.7.1+ but these errors were occurring with older kernels too.)
Thanks,
Martin
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
