Santi Saez wrote:
> 
> Dear Srs,
> 
> I'm getting this error when trying to connect to a Infortrend A16E- 
> G2130-4 storage vía iSCSI.
> 
>> Apr 29 10:24:40 vz-10 kernel: scsi1 : iSCSI Initiator over TCP/IP
>> Apr 29 10:24:41 vz-10 kernel:   Vendor: IFT       Model: A16E- 
>> G2130-4      Rev: 361F
>> Apr 29 10:24:41 vz-10 kernel:   Type:   Direct- 
>> Access                      ANSI SCSI revision: 04
>> Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: 629145600 512-byte  
>> hdwr sectors (322123 MB)
>> Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off
>> Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back
>> Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: 629145600 512-byte  
>> hdwr sectors (322123 MB)
>> Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off
>> Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back
>> Apr 29 10:24:41 vz-10 iscsid: connection1:0 is operational now
>> Apr 29 10:24:44 vz-10 udevd-event[23432]: wait_for_sysfs: waiting  
>> for '/sys/devices/platform/host1/session1/target1:0:0/1:0:0:0/ 
>> ioerr_cnt' failed
>> Apr 29 10:25:06 vz-10 iscsid: Nop-out timedout after 15 seconds on  
>> connection 1:0 state (3). Dropping session.
>> Apr 29 10:25:10 vz-10 iscsid: connection1:0 is operational after  
>> recovery (2 attempts)
>> Apr 29 10:25:36 vz-10 iscsid: Nop-out timedout after 15 seconds on  
>> connection 1:0 state (3). Dropping session.
>> Apr 29 10:25:39 vz-10 iscsid: connection1:0 is operational after  
>> recovery (2 attempts)
>> Apr 29 10:26:05 vz-10 iscsid: Nop-out timedout after 15 seconds on  
>> connection 1:0 state (3). Dropping session.
>> Apr 29 10:26:09 vz-10 iscsid: connection1:0 is operational after  
>> recovery (2 attempts)
>> Apr 29 10:26:34 vz-10 iscsid: Nop-out timedout after 15 seconds on  
>> connection 1:0 state (3). Dropping session.
>> Apr 29 10:26:38 vz-10 iscsid: connection1:0 is operational after  
>> recovery (2 attempts)
>> Apr 29 10:27:03 vz-10 iscsid: Nop-out timedout after 15 seconds on  
>> connection 1:0 state (3). Dropping session.
>> Apr 29 10:27:07 vz-10 iscsid: connection1:0 is operational after  
>> recovery (2 attempts)
>> Apr 29 10:27:32 vz-10 kernel:  sdb:<6>sd 1:0:0:0: SCSI error:  
>> return code = 0x00020000
>> Apr 29 10:27:32 vz-10 kernel: end_request: I/O error, dev sdb,  
>> sector 0
>> Apr 29 10:27:32 vz-10 kernel: Buffer I/O error on device sdb,  
>> logical block 0
>> Apr 29 10:27:32 vz-10 iscsid: Nop-out timedout after 15 seconds on  
>> connection 1:0 state (3). Dropping session.
>> Apr 29 10:27:36 vz-10 iscsid: connection1:0 is operational after  
>> recovery (2 attempts)
>> Apr 29 10:28:02 vz-10 iscsid: Nop-out timedout after 15 seconds on  
>> connection 1:0 state (3). Dropping session.
>> Apr 29 10:28:05 vz-10 iscsid: connection1:0 is operational after  
>> recovery (2 attempts)
>>
> 
> 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.


> 
> The "iscsiadm" holds on:
> 
> [EMAIL PROTECTED]:~
> # iscsiadm -m node --targetname iqn. 
> 2002-10.com.infortrend:raid.sn7511631.10 -p 10.15.17.131 -l
> Login session [iface: default, target: iqn. 
> 2002-10.com.infortrend:raid.sn7511631.10, portal: 10.15.17.131,3260]
> (..)
> 
> It's a strange problem.. I have no errors with CentOS 4.6, what can  
> be the problem? Thanks!!
> 

What are the settings for the PingTimeout, ActiveTimeout and IdleTimeout 
in /etc/iscsi.conf in the 4.6 installation?

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