Hi Mike, [Note: Attachment sent off list so as not to pollute everyone's inbox.]
On 19 May 2010, at 20:14, Mike Christie wrote: > On 05/19/2010 09:20 AM, Anton Altaparmakov wrote: >> Hi Mike, >> >> On 19 May 2010, at 12:48, Mike Christie wrote: >>> On 05/18/2010 05:14 AM, Anton Altaparmakov wrote: >>>> # iscsiadm -m session -P3 >>>> iSCSI Transport Class version 2.0-724 >>>> iscsiadm version 2.0-868 >>>> Target: iqn.2008-02.xenstorenet.nessie:arup301 >>>> Current Portal: 10.10.10.1:3260,1 >>>> Persistent Portal: 10.10.10.1:3260,1 >>>> ********** >>>> Interface: >>>> ********** >>>> Iface Name: default >>>> Iface Transport: tcp >>>> Iface Initiatorname: iqn.2008-02.xenstorenet.hydra:redstone >>>> Iface IPaddress: 10.10.10.2 >>>> Iface HWaddress: default >>>> Iface Netdev: default >>>> SID: 5 >>>> iSCSI Connection State: LOGGED IN >>>> iSCSI Session State: Unknown >>>> Internal iscsid Session State: NO CHANGE >>>> ************************ >>>> Negotiated iSCSI params: >>>> ************************ >>>> HeaderDigest: CRC32C >>>> DataDigest: CRC32C >>> >>> You might need this fix: >>> http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=96b1f96dcab87756c0a1e7ba76bc5dc2add82b88 >> >> Thank you for the suggestion! I just tried it by changing that line, >> recompiling and replacing the SLES 10 libiscsi.ko module with the newly >> compiled one, then stopped the open-iscsi service and ensured the module was >> unloaded and then tried again, this time it loaded the new module (and >> complained it wasn't supported by Novell so definitely loading the new one) >> and it still timed out the same way. )-: >> >> Any other ideas? >> > > Is there anyway you can give me the libiscsi.c, iscsi_tcp.c and if it exists > the libiscsi_tcp.c files for kernel that worked and did not work? Sure, attached... The sp2-iscsi directory is the working one and the sp3-iscsi directory is the non-working one (note it includes the patch that you referenced above, the original SP3 code did not have that). > Or could you also take a ethereal trace for when it worked and when it did > not? Not sure about ethereal. Would tcpdump do? What options would you like me to run it with? Thanks a lot for your help! Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ -- 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 open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
