On 10/26/2011 4:16 PM, Sebastian Riemer wrote:
Are you doing something on the target? In older tools if the target
returned a login error indicating it was not coming back iscsid would
logout the session destroying /dev/sdXs. I am not sure what is in debian's code.
Indeed, Mike's points need to be addresses, what you got is disconnection
on the initiator, and it seems to be initiated by the target side. I don't
think it has something to do with the dma unmapping question I was
posting before.
You have to look on the target logs (if you're using tgt, restart it
with "-d 1"
or issue "tgtadm --mode system --op update --name debug --value on" and
make sure
debug level syslog calls are recorded by the syslog daemon to some file,
e.g
/var/log/messages or alike), and optionally also on the initiator logs,
I would
suggest to start with libiscsi logs (set to 1 all of
/sys/module/libiscsi/parameters/debug_libiscsi_* no need to reload the
module)
This will help you see who disconnecting and what happened before.
Or.
--
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.
