From owner-freebsd-scsi@FreeBSD.ORG Thu May 26 06:15:36 2011 Return-Path: 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 316DD106566B for ; Thu, 26 May 2011 06:15:36 +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 D3D0B8FC12 for ; Thu, 26 May 2011 06:15:35 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1QPTr3-0001wu-9E; Thu, 26 May 2011 09:15:33 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Matthew Jacob In-reply-to: <4DDD08D6.30105@feral.com> References: <4DDBB3F7.20303@feral.com> <4DDD08D6.30105@feral.com> Comments: In-reply-to Matthew Jacob message dated "Wed, 25 May 2011 06:49:10 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 May 2011 09:15:33 +0300 From: Daniel Braniss Message-ID: Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi_initiator and tag opening problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 06:15:36 -0000 > > > On 5/25/2011 12:20 AM, Daniel Braniss wrote: > > ... > > is this somehow detectable? or a list of '[non]complaint' targets is needed? > You probably should decide whether to just use SIMPLE (no matter what) > or have a list. Since it's a violation of SAM I doubt that there is a > way to detect it. > > ... > > any side effects? or should I make it tunable? > > As it stands now for FreeBSD, making them all SIMPLE would probably be > okay. Linux does that apparently. > I'd make it a tunable with the default to SIMPLE. I asked some of the > (now NetApp) Engenio engineers, and their arrays' iSCSI implementation > *does* handle all of the different tag types. I'm inclined to set the default as it was, and only if it doesn't work it can be fixed via the tunable. The reasoning is that it has worked for most targets, including NetAPP, but then again, if the new crop of targets are based on non-compliant ... > > Thanks Matthew, you made my day! > > > > > No problem. Thank you, actually. I'm starting to work more with iSCSI > for my day job which has been an interesting change. I hope it won't interfere with your valuable cooperation! cheers, danny