On 04/12/2011 12:43 PM, Joe Hoot wrote:
I'm trying to understand the following messages:
Apr 12 13:23:52 oim60025001 tgtd: conn_close(88) connection closed 0x94d80c4
1
.... lots of the above messages...
Apr 12 13:37:19 oim60025001 tgtd: abort_task_set(979) found 271 0
.... lots of the above messages...
Apr 12 13:37:27 oim60025001 tgtd: abort_cmd(955) found e9 e
.... lots of the above messages...
Apr 12 13:39:08 oim60025001 tgtd: conn_close(88) connection closed 0xa9ab8ec
1
Does that typically mean that the target has closed the connection or the
initiator?
Might be best to ask the tgtd list, but I think due to the abort
messsages it is probably the initiator if you are using open-iscsi for
the initiator and if you see the abort messages before conn_close ones.
If you see abort ones first, then see conn close ones, then probably a
scsi command is timing out. This causes the scsi layer to have the
initiator abort the command. If the abort fails, the initiator could try
a lun reset or target reset. If we cannot reset or abort the problem
away we drop the connection/session.
On the initiator if you did
echo 1 > /sys/module/libiscsi/parameters/debug_libiscsi_eh
you would see a "wait for relogin" message in /var/log/messages then a
"session reset succeeded" or "failing session reset: Could not log back
into" message. The wait for relogin would match the conn close messages
on the target. Then the success or failed messages indicated if we were
able to relogin.
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
