Judging by target log Eugene has provided, the target performs
implicit shutdown based on initiator-supplied ISID value:
Thu Oct 23 18:24:29 2008 SES2 redmine.cpm.ru ISID[00023d100000]
Thu Oct 23 18:24:29 2008 SES1 Implicit shutdown
Thu Oct 23 18:24:29 2008 CON0 ---- LOGGED_IN(T8) -> FREE
Thu Oct 23 18:24:29 2008 SES1 Starting shutdown
This is done by exactly the code fragment Nick has pointed out yesterday:
644 /*
645 * Section 5.3.5
646 * Session reinstatement is the process of the initiator
647 * logging in with an ISID that is possible active from
648 * the target's perspective. Thus implicitly logging out
649 * the session that corresponds to the ISID and
650 * reinstating a new iSCSI session in its place (with
the
651 * same ISID).
652 */
653 if (bcmp(check->s_isid, s->s_isid, 6) == 0) {
654 queue_prt(s->s_mgmtq, Q_SESS_NONIO,
655 "SES%x Implicit shutdown\n", check->s_num);
656 if (check->s_conn_head->c_state == S5_LOGGED_IN)
657 conn_state(check->s_conn_head, T8);
658 else
659 conn_state(check->s_conn_head, T7);
660 break;
Regards,
Andrey
On Thu, Oct 23, 2008 at 7:00 PM, Eugene Chupriyanov <[EMAIL PROTECTED]> wrote:
>> Eugene, it certainly would be useful to have some
>> time stamps on
>> the 'iscsisnoop.d'. Also if you look at this page:
>> http://blogs.sun.com/ahl/entry/iscsi_dtrace_provider_a
>> nd_other
>> .. maybe you can figure how to get some information
>> on the
>> relevant connection from 'args[0]'.
>>
>> It would be good to see all three outputs:
>> 1. iscsi target debug log
>> 2. 'iscsisnoop.d' output, with timestamps
>> 3. Initiator log
>> .. to get the right sequence and just to try and
>> figure out
>> what is cause and effect.
>> More verbosity from the initiator log may well also
>> help if that's possible.
> Here we are.
> I've modified iscsisnoop.d to include timestamps. So what I did:
> 1) Turned on target_log (file attached)
> 2) Started iscsisnoop.d (see the file attached)
> 3) Started initiator usual way (relevant part of /var/log/messages attached)
> Tried mkfs on attached LUN - the same picture as before. Waited coupld of
> minutes and stopped initiator.
> 4) Started iscsid in foreground with most debugging info (attached
> iscsid.out) but no timestamps there. Repeated creating filesystem - same
> result.
>
> Hope it will help.
>
> Thanks,
> Eugene
> --
> This message posted from opensolaris.org
> _______________________________________________
> storage-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
>
>
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
