Hi Lee,
Actually the problem is not exactly with working of open-iscsi on SuSe.
We have modified open-iscsi to some extent to suit our requirements. Here
is what major change we have done -
In open-iscsi, whole receive processing happens in tcp callback context
whereas in our case, we are
Narender:
I work for SUSE. Please file a SUE bug on this, and please cc me - my work
email is lduncan at novell dot com.
I have a similar setup, i.e. booted SLES 11 SP2 using iSCSI, but I have
seen no such errors. When you file the bug, please include log messages and
a list of initiator HBA
s/SUE bug/SUSE bug/
On Wednesday, June 27, 2012 3:26:25 PM UTC-7, The Lee-Man wrote:
Narender:
I work for SUSE. Please file a SUE bug on this, and please cc me - my work
email is lduncan at novell dot com.
I have a similar setup, i.e. booted SLES 11 SP2 using iSCSI, but I have
seen no
On 06/22/2012 12:45 AM, narender mehra wrote:
I read the latter half of your reply now. Yes, we have iscsi_sw_data_recv
as the recv_actor function. Thanks for the reply.
Hey, what? Are you sure it is called iscsi_sw_data_recv?
I was thinking it should only be either:
iscsi_sw_tcp_recv
or
Sorry for the confusion. It is iscsi_sw_tcp_recv.
On Fri, Jun 22, 2012 at 11:14 PM, Mike Christie micha...@cs.wisc.eduwrote:
On 06/22/2012 12:45 AM, narender mehra wrote:
I read the latter half of your reply now. Yes, we have iscsi_sw_data_recv
as the recv_actor function. Thanks for the
Am using open-iscsi on Suse 10.2, while doing IO, in receive path, the
function iscsi_sw_tcp_recv is not getting called by the tcp_read_sock
function. It manifests in the receive path (Data-in PDUs processing) but
does not always happens at the same moment every time I have put some
printks in
On 06/21/2012 07:39 AM, narender wrote:
Am using open-iscsi on Suse 10.2, while doing IO, in receive path, the
function iscsi_sw_tcp_recv is not getting called by the tcp_read_sock
function. It manifests in the receive path (Data-in PDUs processing) but
does not always happens at the same
Thanks for the prompt reply.
The kernel we are using is Suse 11 SP 2 . This problem is seen
intermittently after a few read have completed.
The callback never gets called resulting in a SCSI timeout.
Is there a pointer to the patch that I can get. That would be highly
appreciated.Thanks again.
