On 04/15/2011 12:22 PM, Mike Christie wrote:
On 04/15/2011 01:43 PM, Ben Greear wrote:
On 04/15/2011 11:37 AM, Mike Christie wrote:
On 04/15/2011 01:18 PM, Mike Christie wrote:

Ok, yeah we have seen this type of setup before and we should be
able to
handle this situation as long as the other controller assumes the IP
and
is ready within node.session.timeo.replacement_timeout seconds.

What is expected behaviour if it *does NOT* become ready by the timeout
expiration?

In /var/log/messsages you would see the message:

session recovery timed out after %d secs

Ahh, I do..and they are timing out after 120 secs.  Wonder if that
races with the deadlock detection logic which also times out at 120 seconds.

Apr 11 20:26:57 net-lanf-3 iscsid: connect to 198.18.163.11:3260 failed (No 
route to host)
Apr 11 20:26:58 net-lanf-3 iscsid: connect to 198.18.164.11:3260 failed (No 
route to host)
Apr 11 20:26:59 net-lanf-3 iscsid: connect to 198.18.162.11:3260 failed (No 
route to host)
Apr 11 20:27:00 net-lanf-3 iscsid: connect to 198.18.161.11:3260 failed (No 
route to host)
Apr 11 20:27:01 net-lanf-3 kernel: session5: session recovery timed out after 
120 secs
Apr 11 20:27:01 net-lanf-3 kernel: session8: session recovery timed out after 
120 secs

Also, even if we fail the time-out, I assume the system shouldn't hang
and panic as it did?

It will for ext3. I believe there is a option for to panic on errors or
not.


The crash I reported was due to the flush process hanging for > 120 seconds,
but maybe that's just because the iscsi timeout is 120 as well.

Perhaps it would have crashed in the file-system a bit later (or not at all) if
I had the process-hang detection at 180s or so, for instance...


Thanks for the help..I have some things to try now and will let you know
how it goes.

Thanks,
Ben

--
Ben Greear <gree...@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

--
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com.
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

Reply via email to