From owner-freebsd-scsi@FreeBSD.ORG Tue May 18 22:20:01 2010 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 AE8541065674 for ; Tue, 18 May 2010 22:20:01 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 8BF078FC0A for ; Tue, 18 May 2010 22:20:01 +0000 (UTC) Received: from [192.168.221.2] (remotevpn [192.168.221.2]) by ns1.feral.com (8.14.3/8.14.3) with ESMTP id o4IMK0ZR046148 for ; Tue, 18 May 2010 15:20:00 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <4BF3128B.4060005@feral.com> Date: Tue, 18 May 2010 15:19:55 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <4BF19453.8090801@feral.com> In-Reply-To: <4BF19453.8090801@feral.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.2.3 (ns1.feral.com [192.168.221.1]); Tue, 18 May 2010 15:20:01 -0700 (PDT) Subject: Re: going rogue: incorporating REPORT_LUNS into the SCSI probe sequence 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: Tue, 18 May 2010 22:20:01 -0000 I'm going to withdraw this- I've found a couple of bugs, and I think it's important to actually deal with the case of no lun 0. > This one is a bit rougher than the others, but I'd like to encourage > some discussion about this. > > The problems presented by not using REPORT LUNS have been getting > uglier and uglier. Any kind of sparse lun arrangement for large JBODs > or RAID units just makes life very painful. > > These changes manage REPORT LUNS for devices > SPC2, and even manage > changes in the list. These changes do *not* address the edge case of > having no attached LUN 0 (which has been known to happen- it's not > illegal). > > I haven't quite finished putting together an action based upon the LUN > INVENTORY MAY HAVE CHANGED ASC/ASCQ, and testing has been somewhat light. > > Still...... > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org"