Bug 172487
| Summary: | Difficulty with some iSCSI targets in iscsi_sfnet | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Andrew J Forgue <forgue> |
| Component: | kernel | Assignee: | Mike Christie <mchristi> |
| Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | jbaron |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHSA-2006-0132 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-03-07 20:38:00 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 168429 | ||
That code was removed becuase it was for a unsupported buggy target. However, our opcode code has a bug that triggers when targets send us bad commands. Could you try this sourceforge release and tell me if this fixes it for you http://www.cs.wisc.edu/~michaelc/linux-iscsi-rhel4.tar If it does I will try to get the fix into the next RHEL update. Until we get this fixed you can also just set IdleTimeout=0 ActiveTimeout=0 so the initiator will not send pings. Thanks for taking the time to fix this up for me.... Here's the output of the build: [forgue@mccoy linux-iscsi-rhel4]$ make Note: using kernel source from /lib/modules/2.6.9-22.0.1.EL.rootsmp/build containing kernel version 2.6.9-22.0.1.EL.rootsmp Note: using kernel config from /lib/modules/2.6.9-22.0.1.EL.rootsmp/build/.config make[1]: Entering directory `/usr/src/kernels/2.6.9-22.0.1.EL.root-smp-i686' CC [M] /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-initiator.o CC [M] /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-attr.o CC [M] /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-session.o CC [M] /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-task.o CC [M] /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-portal.o CC [M] /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-ioctl.o CC [M] /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-network.o CC [M] /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-recv-pdu.o /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-recv-pdu.c: In function `iscsi_recv_pdu': /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-recv-pdu.c:918: error: syntax error before '=' token /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-recv-pdu.c:924: error: `op' undeclared (first use in this function) /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-recv-pdu.c:924: error: (Each undeclared identifier is reported only once /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-recv-pdu.c:924: error: for each function it appears in.) /home/f/forgue/linux-iscsi-rhel4/driver/iscsi-recv-pdu.c:929: error: `opcode' undeclared (first use in this function) make[2]: *** [/home/f/forgue/linux-iscsi-rhel4/driver/iscsi-recv-pdu.o] Error 1 make[1]: *** [_module_/home/f/forgue/linux-iscsi-rhel4/driver] Error 2 make[1]: Leaving directory `/usr/src/kernels/2.6.9-22.0.1.EL.root-smp-i686' make: *** [module] Error 2 Try this: http://www.cs.wisc.edu/~michaelc/linux-iscsi-test2.tar.gz Note that you need the sysfsutils-devel rpm installed. There are also some incompatibily tools so just do this: - tar -zxvf inux-iscsi-test2.tar.gz - cd linux-iscsi.work - make (DO NOT DO MAKE INSTALL!!!!!!) - if you have iscsi_sfnet and scsi_transport_iscsi loaded, rmmod them - While in the linux-iscsi.work dir do a insmod driver/scsi_transport_iscsi.ko insmod driver/iscsi_sfnet.ko - Then from linux-iscsi.work run Linux-i686/obj/iscsid Linux-i686 is the dir for my single proc Intel box, but you may have PPC or smp or some other arch. And tell me if this works for you. Yes, thank you. That seems to work, no more messages on the console about dropping sessions. I formatted and mounted a 150gb volume on the iSCSI target and did not have any errors in dmesg about dropping connections. I think this fixed it. ok, I think we may have missed the window for U3, but I will try since this is minor patch. If not U3 it will be in U4. Until then you can use disable the ping timeout like in comment 2. Thankd for testing. commited in -22.23 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2006-0132.html |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 Description of problem: When using the iSCSI initiator and associated driver for the above kernel, I receive many of the following syslog messages: iscsi-sfnet:host1: Dropping session after receiving unexpected opcode 0xe0 iscsi-sfnet:host1: Session dropped iscsi-sfnet:host1: Waiting 2 seconds before next login attempt iscsi-sfnet:host1: Session established This happens a lot and just demolishes performance and occasionally makes the driver not connect to the target until the next reboot. Previous versions of sfnet's iscsi had this line (marked with +) in iscsi-recv-pdu.c: switch (hdr->opcode) { + case ISCSI_OP_NOOP_IN | 0xc0: /* work-around a bug in the Intel Nov05 target */ case ISCSI_OP_NOOP_IN: handle_nop_in(session, hdr); That line seems to be gone in the RHEL4U2 version of the file. I did all kinds of google searching for what 'Nov05' is, but can't find anything. My iSCSI applicance is at the latest firmware revision from the vendor. I installed the latest SRPM for the kernel and rebuilt it with that line and now iSCSI works like it should. This extra case statement was in iscsi.c and then iscsi.c disappeared[1] and then the case statement re-appeared in iscs-recv-pdu.c[2]. I have no idea why this line of code was removed, I can't find anything in the changelogs or CVS commit logs. Anyways, I would very much prefer not recompiling my kernel every time RHEL releases a new update. [1]: http://cvs.sourceforge.net/viewcvs.py/linux-iscsi/linux-iscsi/driver/Attic/iscsi.c?rev=1.1.2.8&view=markup [2]: http://cvs.sourceforge.net/viewcvs.py/linux-iscsi/linux-iscsi/driver/iscsi-recv-pdu.c?rev=1.33&view=markup Version-Release number of selected component (if applicable): kernel-smp-2.6.9-22.0.1.EL How reproducible: Always Steps to Reproduce: Get an iSCSI target that sends you 0xe0 codes for some reason. The Intransa IP5000 works well. Additional info: