(For anyone reading this thread via Pipermail, you may have noticed
a server outage earlier today. As a result, Pipermail dropped a
couple of posts that registered sucessfully on the 'Jive' forum.
so you may want to check this thread via Jive:
http://www.opensolaris.org/jive/thread.jspa?threadID=90428
to see if you missed any thing interesting...)
Hi Frank,
Ok, the 'Discovery' session is not that critical.
Anyway, I can now say I have seen two snoop captures from you where
the 'InitiatorName' was definitly specified in the logon packet for
a 'Normal' session.
As a further confirmation, try this DTrace script, (with thanks to Jim Dunham
for his great lead here...)
# dtrace -n 'pid$target::check_access:entry { printf("%S",copyinstr(arg1)); }'
-p `pgrep -o iscsitgtd`
dtrace: description 'pid$target::check_access:entry ' matched 1 probe
CPU ID FUNCTION:NAME
0 81788 check_access:entry iqn.1991-05.com.microsoft:mimas\0
0 81788 check_access:entry iqn.1991-05.com.microsoft:mimas\0
^C
Above you can see some test output from one of my systems where I'm
using a Microsoft initiator.
This DTrace script picks out the second argument to the function
'check_access()'
which should print out the 'InitiatorName'.
That function is defined here:
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/iscsi/iscsitgtd/util.c
Ok, it seems the core dump is occuring due to a bad arg to
the 'strcmp' function. We've looked at the ones in line 107 and 141,
but I've noticed there is a third one in line 161.
I wonder if that one be causing a problem?
Best Regards
Nigel Smith
--
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
