Mike Christie wrote:
>> Login session [iiser: iser_connect:connecting to:, port  
>> 0xbc0c
>> face: default, target: iqn.1986-iser: iser_cma_handler:event 0 conn  
>> ffff81022847ce80 id ffff81023eb82a00
>> 03.com.sun:02:91iser: iser_cma_handler:event 2 conn ffff81022847ce80  
>> id ffff81023eb82a00
>> 7071dc-db02-ebf0-9508-d11df2889cda, portal:,3260]
>> iser: iser_create_ib_conn_res:setting conn ffff81022847ce80 cma_id  
>> ffff81023eb82a00: fmr_pool ffff81043edf8d40 qp ffff810247154200
>> iser: iser_cma_handler:event 9 conn ffff81022847ce80 id ffff81023eb82a00
>> iser: iscsi_iser_ep_poll:ib conn ffff81022847ce80 rc = 1
>> iser: iscsi_iser_conn_bind:binding iscsi conn ffff810228385290 to  
>> iser_conn ffff81022847ce80
>> iser: iser_cma_handler:event 10 conn ffff81022847ce80 id  
>> ffff81023eb82a00
>> iser: iscsi_iser_ep_disconnect:ib conn ffff81022847ce80 state 4
>> iser: iser_free_ib_conn_res:freeing conn ffff81022847ce80 cma_id  
>> ffff81023eb82a00 fmr pool ffff81043edf8d40 qp ffff810247154200
>> iser: iser_device_try_release:device ffff81043fee4d40 refcount 1
>> [ snip ]
>> iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
>> iscsiadm: Could not execute operation on all records. Err 107.
>> Any way to get some more robust information regarding "iSCSI login  
>> failure"?
> What are you talking about. You do not have the iser_cmd_handler event 
> numbers memorized yet :) Me neither :( It looks like the target 
> disconnected and there was some sort of iser connection error because 
> the ib_conn state is ISER_CONN_DOWN. The iser guys can diagnose it 
> better for whatever kernel you are using.
What you have here is connection established (event 9) and then 
disconnection (event 10). I suggest that you use logging with the iscsid 
user space daemon to realize better what went wrong. The way I do this 
is: start the service, then logout, then kill the daemon, run it again 
with logging/debug prints open and login manually.

run$ iscsid -d 8 -f > /tmp/iscsid.log 2>&1 &
login$ iscsiadm -m node -T $target -l
logout$ iscsiadm -m node -T $target -u

As for the iser event numbers... it not iser but rather the RDMA CM 
events, they are present in include/rdma/rdma_cm.h at the kernel source 


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

Reply via email to