Santi Saez wrote:
> 
> El 29/04/2008, a las 18:23, Mike Christie escribió:
> 
>>> The problem appears to be related to udevd-event? The system is
>>> running CentOS 5.1, with kernel 2.6.18-53.1.14.el5PAE, and "iscsi-
>>> initiator-utils-6.2.0.865-0.8.el5".
>> The target does not like our nops. If you set
>>
>> node.conn[0].timeo.noop_out_interval = 0
>> node.conn[0].timeo.noop_out_timeout = 0
>>
>> It should fix that problem, but if you could check the target logs for
>> something about a bad PDU or iSCSI protocol error or anything, we can
>> see why this is causing problems.
> 
> Dear Mike,
> 
> I get the same error changing those values at /etc/iscsi/iscsi.conf  
> file and with "iscsiadm":


Not exactly the same error :)

> 
>> # tail -f -n0 -q /var/log/* 2> /dev/null
>> Apr 29 19:28:12 vz-09 iscsid: iSCSI logger with pid=3450 started!
>> Apr 29 19:28:12 vz-09 kernel: scsi2 : iSCSI Initiator over TCP/IP
>> Apr 29 19:28:12 vz-09 kernel:   Vendor: IFT       Model: A16E- 
>> G2130-4      Rev: 361F
>> Apr 29 19:28:12 vz-09 kernel:   Type:   Direct- 
>> Access                      ANSI SCSI revision: 04
>> Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: 629145600 512-byte  
>> hdwr sectors (322123 MB)
>> Apr 29 19:28:12 vz-09 kernel: sdb: Write Protect is off
>> Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: drive cache: write back
>> Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: 629145600 512-byte  
>> hdwr sectors (322123 MB)
>> Apr 29 19:28:12 vz-09 kernel: sdb: Write Protect is off
>> Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: drive cache: write back
>> Apr 29 19:28:13 vz-09 iscsid: transport class version 2.0-724.  
>> iscsid version 2.0-865
>> Apr 29 19:28:13 vz-09 iscsid: iSCSI daemon with pid=3451 started!
>> Apr 29 19:28:13 vz-09 iscsid: Could not read data from db. Using  
>> default and currently negotiated values


Are you doing iscsi boot? Or did you start the iscsi service, try to 
stop it then try to restart it and one of the steps had errors?


>> Apr 29 19:28:13 vz-09 iscsid: connection2:0 is operational now
>> Apr 29 19:28:16 vz-09 udevd-event[3470]: wait_for_sysfs: waiting  
>> for '/sys/devices/platform/host2/session2/target2:0:0/2:0:0:0/ 
>> ioerr_cnt' failed
>> Apr 29 19:28:16 vz-09 iscsid: connection1:0 is operational after  
>> recovery (2 attempts)
>> Apr 29 19:29:02 vz-09 kernel:  sdb:<6> connection2:0: iscsi:  
>> detected conn error (1011)
>> Apr 29 19:29:03 vz-09 iscsid: Kernel reported iSCSI connection 2:0  
>> error (1011) state (3)
>> Apr 29 19:29:06 vz-09 kernel: iscsi: host reset succeeded
>> Apr 29 19:29:06 vz-09 iscsid: connection2:0 is operational after  
>> recovery (2 attempts)
> 

For some reason all IO after the inquiry/report_luns does not seem to be 
getting to the target, or the target is not processing them.

Does the inforterend box have multiple cards/hbas/ports? Does it require 
any ACL type of setup? Do you have to tell it to allow certain initiators?

Are there any errors in the target logs?

--~--~---------~--~----~------------~-------~--~----~
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