On 11/20/2010 02:53 PM, Thomas wrote:
Running with the 232 test kernel, the errors persist.
Nov 20 12:39:52 pxfs02 kernel: connection1:0: detected conn error
If there are no other messages before this it seems that the driver is
dropping the conn either due to some iscsi/scsi eh reason or in reaction
to the target dropping it. I think this means bnx2i_cm_remote_close or
bnx2i_cm_remote_abort or bnx2i_indicate_netevent or the scsi eh were
called. If you were not doing ifdown on the network interface then it is
seems it is the abort or remote close or the scsi eh.
For the abort/remote close case, I would look in the target logs to
check if the target dropped the session.
For the scsi eh case, you can turn on debugging:
echo 1 > /sys/module/libiscsi2/paramters/debug_libiscsi
If this were the problem then you would see "aborting sc" messages
before the conn error 1011 messages.
You received this message because you are subscribed to the Google Groups
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at