Re: open-iscsi fails on SLES 10 SP3 kernel but works on SP2 kernel.
Hi, On 26 May 2010, at 02:11, Mike Christie wrote: On 05/25/2010 08:04 PM, Mike Christie wrote: On 05/19/2010 05:17 PM, Anton Altaparmakov wrote: 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). There does not seem to be anything in there that would cause this. The bug that the patch I referenced was not even in there. On each kernel are you using the same iscsi userspace tools? Could you send me the drivers/scsi/scsi_scan.c from each kernel? Actually do not send me that. With the SLES kernels can you run kernel modules built for one kernel on different kernels? If so then replace the scsi_transport_iscsi.ko, libiscsi.ko, and iscsi_tcp.ko modules on sp3 kernel with the sp2 ones. Before you star the iscsi service you might have to force the insmod of the iscsi modules by doing insmod -f path_to_iscsi_modules/scsi_transport_iscsi.ko insmod -f path_to_iscsi_modules/libiscsi.ko insmod -f path_to_iscsi_modules/iscsi_tcp.ko # insmod -f ./scsi_transport_iscsi.ko insmod: error inserting './scsi_transport_iscsi.ko': -1 Invalid module format So it appears I cannot insert the old modules into the new kernel. I will try to compile the source files on the new kernel and see how that goes... Thanks! Best regards, Anton When you start the iscsi service you might see errors about iser stuff not loading but you can ignore that since we will not be using it. -- 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.
Re: open-iscsi fails on SLES 10 SP3 kernel but works on SP2 kernel.
On 05/25/2010 08:04 PM, Mike Christie wrote: On 05/19/2010 05:17 PM, Anton Altaparmakov wrote: 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). There does not seem to be anything in there that would cause this. The bug that the patch I referenced was not even in there. On each kernel are you using the same iscsi userspace tools? Could you send me the drivers/scsi/scsi_scan.c from each kernel? Actually do not send me that. With the SLES kernels can you run kernel modules built for one kernel on different kernels? If so then replace the scsi_transport_iscsi.ko, libiscsi.ko, and iscsi_tcp.ko modules on sp3 kernel with the sp2 ones. Before you star the iscsi service you might have to force the insmod of the iscsi modules by doing insmod -f path_to_iscsi_modules/scsi_transport_iscsi.ko insmod -f path_to_iscsi_modules/libiscsi.ko insmod -f path_to_iscsi_modules/iscsi_tcp.ko When you start the iscsi service you might see errors about iser stuff not loading but you can ignore that since we will not be using it. -- 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.
Re: open-iscsi fails on SLES 10 SP3 kernel but works on SP2 kernel.
On 05/19/2010 05:17 PM, Anton Altaparmakov wrote: Not sure about ethereal. Would tcpdump do? What options would you like me to run it with? If using tcpdump is easier than trying to use the old modules on the new kernel then do that. Maybe we will have to do both to rule out the iscsi layer. You can just run tcpdump with the defaults: tcpdump -i ethXYZ -w iscsi-tcp.out -- 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.
Re: open-iscsi fails on SLES 10 SP3 kernel but works on SP2 kernel.
On 18 May 2010 at 11:14, Anton Altaparmakov wrote: Hi, We upgraded from SLES 10 SP2 (x86_64) to SLES 10 SP3 (x86_64) which caused our open-iscsi to iscsitarget connections to fail. Downgrading to the SP2 kernel makes it work again. Using the SP3 kernel running we see: Did you just install the SP§, or did you install SP3 + Updates? (Just being curious) [...] Regards, Ulrich -- 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.
Re: open-iscsi fails on SLES 10 SP3 kernel but works on SP2 kernel.
Hi Ulrich, On 19 May 2010, at 07:35, Ulrich Windl wrote: On 18 May 2010 at 11:14, Anton Altaparmakov wrote: We upgraded from SLES 10 SP2 (x86_64) to SLES 10 SP3 (x86_64) which caused our open-iscsi to iscsitarget connections to fail. Downgrading to the SP2 kernel makes it work again. Using the SP3 kernel running we see: Did you just install the SP§, or did you install SP3 + Updates? (Just being curious) + Updates. And I have been trying every kernel update (for about two months now) and it always fails so I have had to downgrade back to the SP2 kernel each time... I guess I ought to try a vanilla SP3 kernel at some point to see if that makes it work. It is a production system so doing testing is very difficult when reboots are needed... 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.
Re: open-iscsi fails on SLES 10 SP3 kernel but works on SP2 kernel.
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 -- 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.
Re: open-iscsi fails on SLES 10 SP3 kernel but works on SP2 kernel.
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? Or could you also take a ethereal trace for when it worked and when it did not? -- 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.
Re: open-iscsi fails on SLES 10 SP3 kernel but works on SP2 kernel.
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.
