Re: Data Digest - Unit Attention Problem
Mike, Zipped log sent. The newer code is reporting a 1015 error on the check response but not on the Inquiry response. Thanks, -Joe On Apr 21, 1:48 pm, Mike Christie wrote: > Joer wrote: > > Mike, > > This the stock RHEL5.2 kernel. > > Could you try the kernel modules here > ttp://www.open-iscsi.org/bits/open-iscsi-2.0-870.3.debug.tar.gz > Just do > > tar -zxvf open-iscsi-2.0-870.3.debug.tar.gz > cd open-iscsi-2.0-870.3.debug/kernel > make > > service iscsi stop > modprobe -r iscsi_tcp > insmod scsi_transport_iscsi.ko > insmod libiscsi.ko > insmod iscsi_tcp.ko > > Then > service iscsi start > and retry your test. > > Send all the log outpout. There should be a lot. > > > > > -joe > > > On Apr 21, 9:18 am, Mike Christie wrote: > >> Joer wrote: > >>> Mike, > >>> Response in line > >>> On Apr 20, 5:14 pm, Mike Christie wrote: > Joer wrote: > > A few more comments on this failure: > > This may be a problem with how the check response is being processed > > by the iSCSI stack...possibly due to data digest. > > The Inquiry command goes out, the response is received with data > > digest, and appears to be accepted. A Test Unit Ready command then > > goes out, response received, and 500 ms later the initiator attempts > > to open a new connection/login. The target then resets the original > > TCP connection. This is repeated several times > Is this easy to replicated? Does it happen every time? > >>> Yes, but only with data digest. The cases that fail are data digest > >>> only, header + data digest. > Were you using the initiator that comes with RHEL 5.2 or 2.0-869.2 from > open-iscsi.org? > >>> I am using the initiator from open-iscsi.org. > >> What kernel are you using? Is it a RHEL one or upstream one on RHEL?- Hide > >> quoted text - > > >> - Show quoted text -- 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 open-iscsi@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 -~--~~~~--~~--~--~---
Re: Data Digest - Unit Attention Problem
Joer wrote: > Mike, > This the stock RHEL5.2 kernel. Could you try the kernel modules here ttp://www.open-iscsi.org/bits/open-iscsi-2.0-870.3.debug.tar.gz Just do tar -zxvf open-iscsi-2.0-870.3.debug.tar.gz cd open-iscsi-2.0-870.3.debug/kernel make service iscsi stop modprobe -r iscsi_tcp insmod scsi_transport_iscsi.ko insmod libiscsi.ko insmod iscsi_tcp.ko Then service iscsi start and retry your test. Send all the log outpout. There should be a lot. > -joe > > On Apr 21, 9:18 am, Mike Christie wrote: >> Joer wrote: >>> Mike, >>> Response in line >>> On Apr 20, 5:14 pm, Mike Christie wrote: Joer wrote: > A few more comments on this failure: > This may be a problem with how the check response is being processed > by the iSCSI stack...possibly due to data digest. > The Inquiry command goes out, the response is received with data > digest, and appears to be accepted. A Test Unit Ready command then > goes out, response received, and 500 ms later the initiator attempts > to open a new connection/login. The target then resets the original > TCP connection. This is repeated several times Is this easy to replicated? Does it happen every time? >>> Yes, but only with data digest. The cases that fail are data digest >>> only, header + data digest. Were you using the initiator that comes with RHEL 5.2 or 2.0-869.2 from open-iscsi.org? >>> I am using the initiator from open-iscsi.org. >> What kernel are you using? Is it a RHEL one or upstream one on RHEL?- 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 open-iscsi@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 -~--~~~~--~~--~--~---
Re: Data Digest - Unit Attention Problem
Mike, This the stock RHEL5.2 kernel. -joe On Apr 21, 9:18 am, Mike Christie wrote: > Joer wrote: > > Mike, > > Response in line > > > On Apr 20, 5:14 pm, Mike Christie wrote: > >> Joer wrote: > >>> A few more comments on this failure: > >>> This may be a problem with how the check response is being processed > >>> by the iSCSI stack...possibly due to data digest. > >>> The Inquiry command goes out, the response is received with data > >>> digest, and appears to be accepted. A Test Unit Ready command then > >>> goes out, response received, and 500 ms later the initiator attempts > >>> to open a new connection/login. The target then resets the original > >>> TCP connection. This is repeated several times > >> Is this easy to replicated? Does it happen every time? > > Yes, but only with data digest. The cases that fail are data digest > > only, header + data digest. > >> Were you using the initiator that comes with RHEL 5.2 or 2.0-869.2 from > >> open-iscsi.org? > > I am using the initiator from open-iscsi.org. > > What kernel are you using? Is it a RHEL one or upstream one on RHEL?- 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 open-iscsi@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 -~--~~~~--~~--~--~---
Re: Data Digest - Unit Attention Problem
Joer wrote: > Mike, > Response in line > > On Apr 20, 5:14 pm, Mike Christie wrote: >> Joer wrote: >>> A few more comments on this failure: >>> This may be a problem with how the check response is being processed >>> by the iSCSI stack...possibly due to data digest. >>> The Inquiry command goes out, the response is received with data >>> digest, and appears to be accepted. A Test Unit Ready command then >>> goes out, response received, and 500 ms later the initiator attempts >>> to open a new connection/login. The target then resets the original >>> TCP connection. This is repeated several times >> Is this easy to replicated? Does it happen every time? > Yes, but only with data digest. The cases that fail are data digest > only, header + data digest. >> Were you using the initiator that comes with RHEL 5.2 or 2.0-869.2 from >> open-iscsi.org? > I am using the initiator from open-iscsi.org. What kernel are you using? Is it a RHEL one or upstream one on RHEL? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: Data Digest - Unit Attention Problem
Mike, Response in line On Apr 20, 5:14 pm, Mike Christie wrote: > Joer wrote: > > A few more comments on this failure: > > This may be a problem with how the check response is being processed > > by the iSCSI stack...possibly due to data digest. > > > The Inquiry command goes out, the response is received with data > > digest, and appears to be accepted. A Test Unit Ready command then > > goes out, response received, and 500 ms later the initiator attempts > > to open a new connection/login. The target then resets the original > > TCP connection. This is repeated several times > > Is this easy to replicated? Does it happen every time? Yes, but only with data digest. The cases that fail are data digest only, header + data digest. > > Were you using the initiator that comes with RHEL 5.2 or 2.0-869.2 from > open-iscsi.org? I am using the initiator from open-iscsi.org. > > > > > Is it possible that the check response with data digest is not being > > handled correctly? > > > The /var/log/message contains a series of the following messages: > > > connection2:0:0 detected conn error (1011) > > Do you see any 1015 errors? 1015 is for data digest errors. 1011 is > generic connection problems or cases where we dropped it for some > generic reason. Solid 1011 errors. I have gone over the response trace looking for PDU errors of any kind and could not find any. > > Is there anything else in the log? Something about a ping or nop timing out? Not that I could see. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: Data Digest - Unit Attention Problem
On 20 Apr 2009 at 13:17, Joer wrote: > > A few more comments on this failure: > This may be a problem with how the check response is being processed > by the iSCSI stack...possibly due to data digest. > > The Inquiry command goes out, the response is received with data > digest, and appears to be accepted. A Test Unit Ready command then > goes out, response received, and 500 ms later the initiator attempts > to open a new connection/login. The target then resets the original > TCP connection. This is repeated several times Hi! The target cannot reset the connection, because the SCSI target knows nothing about the transport connection. Only the iSCSI target software could reset the connection, but why would it do so? [...] 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-iscsi@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 -~--~~~~--~~--~--~---
Re: Data Digest - Unit Attention Problem
Joer wrote: > A few more comments on this failure: > This may be a problem with how the check response is being processed > by the iSCSI stack...possibly due to data digest. > > The Inquiry command goes out, the response is received with data > digest, and appears to be accepted. A Test Unit Ready command then > goes out, response received, and 500 ms later the initiator attempts > to open a new connection/login. The target then resets the original > TCP connection. This is repeated several times Is this easy to replicated? Does it happen every time? Were you using the initiator that comes with RHEL 5.2 or 2.0-869.2 from open-iscsi.org? > > Is it possible that the check response with data digest is not being > handled correctly? > > The /var/log/message contains a series of the following messages: > > connection2:0:0 detected conn error (1011) > Do you see any 1015 errors? 1015 is for data digest errors. 1011 is generic connection problems or cases where we dropped it for some generic reason. Is there anything else in the log? Something about a ping or nop timing 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-iscsi@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 -~--~~~~--~~--~--~---
Re: Data Digest - Unit Attention Problem
A few more comments on this failure: This may be a problem with how the check response is being processed by the iSCSI stack...possibly due to data digest. The Inquiry command goes out, the response is received with data digest, and appears to be accepted. A Test Unit Ready command then goes out, response received, and 500 ms later the initiator attempts to open a new connection/login. The target then resets the original TCP connection. This is repeated several times Is it possible that the check response with data digest is not being handled correctly? The /var/log/message contains a series of the following messages: connection2:0:0 detected conn error (1011) On Apr 17, 9:17 am, Joer wrote: > I ran into an odd interaction between having Data Digest enabled for a > session and the classic Unit Attention check condition for the first > command issued during a session other than Inquiry. My base setup is > as follows: > > Open iSCSI Initiator: 2.0-869.2 > RHEL 5.2 32 bit running in an ESX VM > > My test has four target entities behind a dual portal -portal group. > The targets are setup to negotiate digest as follow: > Target1: no header digest / no data digest > Target2: no header digest / data digest > Target3: header digest / no data digest > Target4: header digest / data digest > > The problem: > Open iSCSI posts a connection error and resets the connection when the > Unit Attention check condition is received on Targets 2 and 4 > following a Test Unit Ready command. My first guess was that there > was a problem with Data Digest generated by for the response PDU > containing the check. However, the Wireshark capture performed on the > nitiator side is saying the digest is good. I checked the response > PDU format and padding and it looks correct. > > Has anyone seen anything like this before? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
