From owner-freebsd-scsi@FreeBSD.ORG  Mon Apr 13 09:28:44 2009
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5BC34106566B
	for <freebsd-scsi@freebsd.org>; Mon, 13 Apr 2009 09:28:44 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84])
	by mx1.freebsd.org (Postfix) with ESMTP id 0EBA48FC14
	for <freebsd-scsi@freebsd.org>; Mon, 13 Apr 2009 09:28:43 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by kabab.cs.huji.ac.il with esmtp
	id 1LtIT3-0006iC-LG; Mon, 13 Apr 2009 12:28:41 +0300
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: "Daisuke Aoyama" <aoyama@peach.ne.jp>
In-reply-to: <44FFCAD8FBB0416FAFFFA879A92C43DF@artemis> 
References: <44FFCAD8FBB0416FAFFFA879A92C43DF@artemis>
Comments: In-reply-to "Daisuke Aoyama" <aoyama@peach.ne.jp>
	message dated "Mon, 13 Apr 2009 10:27:53 +0900."
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 13 Apr 2009 12:28:41 +0300
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1LtIT3-0006iC-LG@kabab.cs.huji.ac.il>
Cc: freebsd-scsi@freebsd.org
Subject: Re: iSCSI initiator questions 
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2009 09:28:44 -0000

> Hi all,
> 
> I have a trouble that FreeBSD initiator caused to panic when umount
> after writing many files to the iSCSI disk. (w/softupdate)
can you tell me where is panic'ed?

> It seems that my istgt corrupted. Then, when I was going to have
> made the digest function effective for diagnostic, I encountered
> a further problem.
> 
> iSCSI initiator(2.1.1) crashed when HeaderDigest was specified and
> the connection was tried. (DataDigest caused the system to hang)
> Has not it been supported yet?

was never finished!, I guess I need to get on with it.

> 
> Note: istgt's digest function was tested by Microsoft's initiators.
> HeaderDigest was also tested by Open-iSCSI initiator (CentOS 5.2).
> 

> This is another question. Is the following code an expected code?
> Why is Head of Queue tag mapped to Ordered Queue tag attribute?
> 
> /usr/src/sys/dev/iscsi/initiator/iscsi_subr.c
> >     case MSG_SIMPLE_Q_TAG:     cmd->attr = iSCSI_TASK_SIMPLE;  break;
> >     case MSG_HEAD_OF_Q_TAG:    cmd->attr = iSCSI_TASK_ORDER;   break;
> >     case MSG_ORDERED_Q_TAG:    cmd->attr = iSCSI_TASK_HOFQ;    break;
> >     case MSG_ACA_TASK:         cmd->attr = iSCSI_TASK_ACA;     break;
> 
the above is a cut-n-paste error
it should be:
     case MSG_HEAD_OF_Q_TAG:	cmd->attr = iSCSI_TASK_HOFQ;	break;
     case MSG_ORDERED_Q_TAG:	cmd->attr = iSCSI_TASK_ORDER;	break;
goot catch!

danny