On 10/30/2011 08:01 AM, Vincent Pelletier wrote:
On Dec 7 2010, 11:12 pm, Mike Christie micha...@cs.wisc.edu wrote:
It could, but you should be ok. If the notification that the connection
is dead comes after IO is sent then we would try to send IO to the
network layer, but the iscsi layer
On Dec 7 2010, 11:12 pm, Mike Christie micha...@cs.wisc.edu wrote:
It could, but you should be ok. If the notification that the connection
is dead comes after IO is sent then we would try to send IO to the
network layer, but the iscsi layer would eventually figure things out
and end up
Hi.
A short update first: I don't have this problem on any later suspend attempt
(~4 so far, from a few dozen of minutes suspend to several hours).
And a disclaimer: my kernel is tainted. Nvidia proprietary driver. Yuck.
Feel free to blame the problems on it, I need a motivation to switch this
hi,
I want to know ,when we didn't login using -I iface ,then how
default interface figure out which interface to use to connect. please
explain.
thanks
vipul vaid
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email
Hi,
I develop s/w for a switch. I would like to discover iSCSI
sessions that pass through my switch.
For this I feel that it is not enough to snoop on just TCP-SYN
messages. According to me, TCP-SYN messages are sent during TCP-
Session establishment. I feel that I should snoop on 0X03
On 10/31/2011 05:10 AM, Sita Allamudi wrote:
Hi,
I develop s/w for a switch. I would like to discover iSCSI
sessions that pass through my switch.
For this I feel that it is not enough to snoop on just TCP-SYN
messages. According to me, TCP-SYN messages are sent during TCP-
Session
On 10/31/2011 08:15 AM, vipul vaid wrote:
hi,
I want to know ,when we didn't login using -I iface ,then how
default interface figure out which interface to use to connect. please
explain.
It depends. It will log into all sessions that are using the default
iface for that portal. Or if you
On 10/31/2011 03:26 PM, Vincent Pelletier wrote:
Hi.
A short update first: I don't have this problem on any later suspend attempt
(~4 so far, from a few dozen of minutes suspend to several hours).
And a disclaimer: my kernel is tainted. Nvidia proprietary driver. Yuck.
Feel free to blame