On 04/15/2010 04:33 AM, Christian Iversen wrote:
What about these timeouts?

node.session.err_timeo.abort_timeout = x
node.session.err_timeo.lu_reset_timeout = y
node.session.err_timeo.host_reset_timeout = z

I would just use the defaults.

What are reasonable values for x, y and z, and when are they used?

If there is a low-level error, I'd like iscsi to detect this quickly and
reconnect right away. (this will happen when there's a failover). Will
the following settings work for this purpose:

node.conn[0].timeo.noop_out_interval = 2
node.conn[0].timeo.noop_out_timeout = 2
node.session.timeo.replacement_timeout = 86400


I'll use this then.

Per my understanding: This will ping the server every 2. seconds, and
wait 2 seconds for a reply. If a connection problem is discovered, the
client will try for 24 hours (86400 seconds) to reestablish a connection
before giving up and returning IO errors to higher layers.

Is this correct? From your description it seems like replacement_timeout


= 0 would cause immediate IO errors in case of connection problems? Or
did I misunderstand?

Yeah, on newer versions 0 causes the IO to be failed immediately. I
wrote that wrong before.

Was it different on old versions?

Yes, it was different in older versions. If your iscsid.conf does not have that info about -1 and 0, then you have older tools and those tools did not let you set the value to 0. If you did the iscsi tools would spit out an error in /var/log/messages saying it was an invalid value and that it was going to use the default 120 instead. And if you tried to use -1 then it could overflow and you end up with all kinds of weirdness.

You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to