[EMAIL PROTECTED] wrote:
> Hi Mike,
> 
> using the Wasabi target and the latest open-iscsi git version (as of
> today)
> I still get the errors, which are according to the Wasabi log a time
> out problem.
> It only happens when logging in, which used to take about one second
> or less,
> but now 5-10 seconds. The messages log on the initiator shows this:
> 
> scsi6 : iSCSI Initiator over TCP/IP
>  connection1:0: detected conn error (1011)
>  connection1:0: detected conn error (1011)
>  connection1:0: detected conn error (1011)
>  connection1:0: detected conn error (1011)
> scsi scan: 66 byte inquiry failed.  Consider BLIST_INQUIRY_36 for this
> device


It looks like it is not liking the inquiry command the scsi layer sends 
it. Do you see anything about bad/invalid scsi commands or something 
about INQRUIYs in the log?

What kernel are you using? I thought from the beginning of the thread 
you were using 2.6.18-53.1.14.el. Is that right?


> scsi 6:0:0:0: Direct-Access     Wasabi   WSB/iSCSI        0401 PQ: 0
> ANSI: 5
> sd 6:0:0:0: [sdb] 327680000 512-byte hardware sectors (167772 MB)
> sd 6:0:0:0: [sdb] Write Protect is off
> sd 6:0:0:0: [sdb] Mode Sense: 5b 00 00 08
> sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> sd 6:0:0:0: [sdb] 327680000 512-byte hardware sectors (167772 MB)
> sd 6:0:0:0: [sdb] Write Protect is off
> sd 6:0:0:0: [sdb] Mode Sense: 5b 00 00 08
> sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
>  sdb: sdb1
> sd 6:0:0:0: [sdb] Attached SCSI disk
> sd 6:0:0:0: Attached scsi generic sg2 type 0
> 
> 
> Albert
> 
> On May 8, 11:46 pm, Mike Christie <[EMAIL PROTECTED]> wrote:
>> a s p a s i a wrote:
>>
>>
>>
>>>> Are you using 869 and do you also see the nop out timeout messages or do
>>>> you just see these connection error messages?
>>> just the above connections errors...
>>> 865 version:
>>> [EMAIL PROTECTED] ~]# iscsiadm -V
>>> iscsiadm version 2.0-865
>>> [EMAIL PROTECTED] ~]# iscsistart -v
>>> iscsistart version 2.0-865
>>> [EMAIL PROTECTED] ~]# modinfo scsi_transport_iscsi
>>> filename:
>>> /lib/modules/2.6.18-53.1.14.el5/kernel/drivers/scsi/scsi_transport_iscsi.ko
>>> version:        2.0-865
>>>> Yeah, read the README section 8 for how to modify the nop and replacment
>>>> timeout settings for iscsi root.
>>> yeah ... i'll do so .. maybe adjust and see if it reappears ...
>>> in searching through current /var/log/messages, seems like the errors
>>> only appeared twice yesterday and once this morning ..
>>> no big deal, but interesting to check.
>> You want to make sure you are using 2.0-865.15 if you are using the 865
>> series. There was a bug in the early 865 releases where during writes we
>> were not tracking data right and we would or the target would drop the
>> session (you would see the error messages you posted about) to get us
>> back on track.
> > 


--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to