On 03/25/2011 09:27 AM, Matthew Richardson wrote:
I'm currently experiementing with changing the timeouts etc for the
iscsi client when connecting to an IET target.
At present, I have it all working such that if I temporarily disconnect
and reconnect the target (cable unplug), I see the following in the logs:
Mar 25 14:14:51 pcw3571 kernel: connection1:0: detected conn error (1011)
Mar 25 14:14:51 pcw3571 iscsid: Kernel reported iSCSI connection 1:0
error (1011) state (3)
Mar 25 14:14:56 pcw3571 iscsid: connect to 192.168.140.10:3260 failed
(No route to host)
Mar 25 14:15:00 pcw3571 iscsid: connection1:0 is operational after
recovery (2 attempts)
However any disk writes to the device block for almost exactly 360 seconds.
How do you know they are blocked? Do you mean they are not getting sent
to the target? If so can you send do
echo 1 > /sys/module/libiscsi/parameters/debug_libiscsi_eh
echo 1 > /sys/module/libiscsi/parameters/debug_libiscsi_session
echo 1 > /sys/module/libiscsi/parameters/debug_libiscsi_conn
echo 1 > /sys/module/iscsi_tcp/parameters/debug_iscsi_tcp
then run your test and then send all of the /var/log/messages.
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
