Re: [linux-iscsi-users] RH4, initiator errors

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

On Wed, 2006-04-19 at 11:17 +0400, pr...@ro... wrote:
> Hello.
> 
> I'm using RH4 2.6.9-22 for target version 0.4.5 and the
> same maching RH4 2.6.9-22 with standart package

~~~~~~~~~~~~~ do not use same box for both ini and target.

> iscsi-initiator-utils as initiator.
> 
> At target side i splice 20G at IDE disk as /dev/hdd3. This
> is config /etc/ietd.conf
> 
> Target iqn.2006-04.net.eltel:storage.st
> Lun 3 /dev/hdd3 fileio
> MaxConnections         3
> ImmediateData   yes
> Alias LVMVOL2
> 
> At initiator side config /etc/iscsi.conf
> 
> DiscoveryAddress=192.168.212.192
>   Username=userid
>   Password=superpasswor
> 
> 
> After i start target daemon and initiator, all looks OK
> 
> #iscsi-ls
> *******************************************************************************
> SFNet iSCSI Driver Version ...4:0.1.11(12-Jan-2005)
> *******************************************************************************
> TARGET NAME             : iqn.2006-04.net.eltel:storage.st
> TARGET ALIAS            :
> HOST ID                 : 2
> BUS ID                  : 0
> TARGET ID               : 0
> TARGET ADDRESS          : 192.168.212.192:3260,1
> SESSION STATUS          : ESTABLISHED AT Wed Apr 19
> 11:05:44 EDT 2006
> SESSION ID              : ISID 00023d000001 TSIH 300
> *******************************************************************************
> 
> iSCSI disk emerge as /dev/sda on initiator. I'm use fdisk
> to create partition and then trying to create ext3 fs. on
> it
> #mkfs.ext3 /dev/sda1
> .....
> Creating journal (8192 blocks): done
> Writing superblocks and filesystem accounting information:
> Warning, had trouble writing out superblocks.done
> .....
> 
> ext3 created with warning. At logs i see
> Apr 19 11:05:28 initiator kernel: iscsi-sfnet:host2: Waking
> tx_thread to send task mgmt function itt 402
> Apr 19 11:05:28 initiator kernel:
> handle_management_functions(1137) d9859d84: 2 188 1
> Apr 19 11:05:28 initiator kernel: iscsi-sfnet:host2: task
> mgmt itt 402 rejected (0x5)
> Apr 19 11:05:28 initiator kernel: iscsi-sfnet:host2:
> Sending ABORT TASK for task itt 368
> Apr 19 11:05:28 initiator kernel: iscsi-sfnet:host2: Waking
> tx_thread to send task mgmt function itt 403
> Apr 19 11:05:28 initiator kernel:
> handle_management_functions(1137) d9859d84: 2 188 1
> Apr 19 11:05:28 initiator kernel: iscsi-sfnet:host2: task
> mgmt itt 403 rejected (0x5)
> Apr 19 11:05:28 initiator kernel: iscsi-sfnet:host2:
> Sending ABORT TASK for task itt 369
> Apr 19 11:05:28 initiator kernel: iscsi-sfnet:host2: Waking
> tx_thread to send task mgmt function itt 404
> Apr 19 11:05:28 initiator kernel:
> handle_management_functions(1137) d9859d84: 2 188 1
> Apr 19 11:05:28 initiator kernel: iscsi-sfnet:host2: task
> mgmt itt 404 rejected (0x5)
> Apr 19 11:05:28 initiator kernel: iscsi-sfnet:host2:
> Sending ABORT TASK for task itt 370
> Apr 19 11:05:28 initiator kernel: iscsi-sfnet:host2: Waking
> tx_thread to send task mgmt function itt 405
> 
> and this
> 
> Apr 19 11:05:44 initiator kernel: iscsi-sfnet:host2:
> Failing command cdb 0x2a task 367 with return code = 0x20
> 000
> Apr 19 11:05:44 initiator kernel: iscsi-sfnet:host2:
> Failing command cdb 0x2a task 368 with return code = 0x20
> 000
> Apr 19 11:05:44 initiator kernel: iscsi-sfnet:host2:
> Failing command cdb 0x2a task 369 with return code = 0x20
> 000
> Apr 19 11:05:44 initiator kernel: iscsi-sfnet:host2:
> Failing command cdb 0x2a task 370 with return code = 0x20
> 000
> Apr 19 11:05:44 initiator kernel: iscsi-sfnet:host2:
> Failing command cdb 0x2a task 371 with return code = 0x20
> 000
> 
> after that session is dropped
> 
> Apr 19 11:05:44 initiator kernel: iscsi-sfnet:host2:
> Session dropped
> Apr 19 11:05:44 initiator kernel: iscsi-sfnet:host2:
> Waiting 2 seconds before next login attempt
> Apr 19 11:05:44 initiator kernel: close_conn(592) 8
> Apr 19 11:05:44 initiator kernel: iscsi-sfnet:host2: Login
> phase timed out, timeout was set for 10 secs
> Apr 19 11:05:44 initiator kernel: iscsi-sfnet:host2: Login
> I/O error, failed to receive a PDU
> Apr 19 11:05:44 initiator kernel: iscsi-sfnet:host2:
> Waiting 1 seconds before next login attempt
> Apr 19 11:05:44 initiator kernel: iscsi-sfnet:host2:
> replacement session time out after 15 seconds, drop 24776
> 46, now 2492646, failing all commands
> 
> And device not ready
> 
> Apr 19 11:05:44 initiator kernel: Device sda not ready.
> Apr 19 11:05:44 initiator kernel: end_request: I/O error,
> dev sda, sector 5768496
> Apr 19 11:05:44 initiator kernel: Buffer I/O error on
> device sda1, logical block 721058
> Apr 19 11:05:44 initiator kernel: lost page write due to
> I/O error on sda1
> Apr 19 11:05:44 initiator kernel: Buffer I/O error on
> device sda1, logical block 721059
> Apr 19 11:05:44 initiator kernel: lost page write due to
> I/O error on sda1
> 
> 
> Can you help me to find a solution? I'm tried to connect to
> target from Windows XP initiator, all works OK.
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> linux-iscsi-users mailing list
> lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-iscsi-users