Sorry for the confusion, we had 2 seperate systems, and I pulled the onfo from the wrong one.
The system with the issue turns out to be RHEL 5.2 with this kernel: 2.6.18-53.1.19.0.1.el5 I'll try and reproduce and get a packet capture On Apr 28, 3:28 pm, Mike Christie <[email protected]> wrote: > On 04/28/2010 02:07 PM, maguar887 wrote: > > > Mike, > > > Thanks for the info! > > > Do you know exactly which kernel it was patched in? > > what is available to us is: > > 2.6.18-194.0.0.0.4.el5Matt > > Forget the upgrade your kernel comment. The bug I was thinking about was > fixed in the kernel you were using, 2.6.18-92.1.6.0.2.el5 (that is > actually the kernel for RHEL 5.2 but you said you were using 5.3 btw). > > Could you get me a ethereal trace, so I can see if the target is failing > the IO on us? > > > > > > > > > Matt > > On Apr 28, 1:58 pm, Mike Christie<[email protected]> wrote: > >> On 04/28/2010 12:56 PM, Mike Christie wrote: > > >>> On 04/28/2010 12:43 PM, Mike Christie wrote: > >>>> On 04/28/2010 10:40 AM, maguar887 wrote: > >>>>> We are currently running open iscsi version 2.0-871 on RHEL 5.3 > >>>>> (2.6.18-92.1.6.0.2.el5) against a Dell Equallogic iScsi SAN group > >>>>> (firmware 4.3.5) > > >>>> You need to upgrade your kernel. It had a bug with eql targets in the > >>>> async logout path. It is fixed in 5.4 and 5.5 kernels. > > >>> Actually it was fixed in 5.3 too. > > >>> The weird thing here is that we get this error *before* we get the async > >>> logout request. > > >>> Do you have multiple sessions? Is sdt accessed through session 22 (run > >>> iscsiadm -m session -P 3 to see) or a different session? If a different > >>> session is there more log and can you send it? > > >> Could you also take a ethereal trace? > > >> Looking at the iscsi code for that kernel the only place to get > >> 0x00070000 seems to be this: > > >> if (rhdr->response != ISCSI_STATUS_CMD_COMPLETED) { > >> sc->result = DID_ERROR<< 16; > >> goto out; > >> } > > >> which means the target did not complete the command. The > >> initiator/scsi-layer would have retried this command up to 5 times > >> before failing. > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "open-iscsi" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]. > >> For more options, visit this group > >> athttp://groups.google.com/group/open-iscsi?hl=en.-Hide quoted text - > > >> - Show quoted text - > > -- > You received this message because you are subscribed to the Google Groups > "open-iscsi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/open-iscsi?hl=en.- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
