From owner-freebsd-scsi@FreeBSD.ORG Thu Apr 5 20:01:30 2012 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 C0844106566C; Thu, 5 Apr 2012 20:01:30 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 690028FC08; Thu, 5 Apr 2012 20:01:30 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id q35K1OOY065141; Thu, 5 Apr 2012 14:01:24 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q35K1ONp065140; Thu, 5 Apr 2012 14:01:24 -0600 (MDT) (envelope-from ken) Date: Thu, 5 Apr 2012 14:01:24 -0600 From: "Kenneth D. Merry" To: "Desai, Kashyap" Message-ID: <20120405200124.GA64019@nargothrond.kdm.org> References: <20120404152801.GA70760@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Cc: "freebsd-scsi@freebsd.org" , "gibbs@freebsd.org" , "McConnell, Stephen" Subject: Re: FreeBSD multi Lun detection query 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, 05 Apr 2012 20:01:30 -0000 On Wed, Apr 04, 2012 at 23:11:22 +0530, Desai, Kashyap wrote: > > > > -----Original Message----- > > From: Kenneth D. Merry [mailto:ken@freebsd.org] > > Sent: Wednesday, April 04, 2012 8:58 PM > > To: Desai, Kashyap > > Cc: freebsd-scsi@freebsd.org; McConnell, Stephen; gibbs@freebsd.org > > Subject: Re: FreeBSD multi Lun detection query > > > > On Wed, Apr 04, 2012 at 11:03:04 +0530, Desai, Kashyap wrote: > > > Hi, > > > > > > Our test team has one test case, where they need to verify multi lun > > detection by FreeBS8.2 OS. > > > Here are the steps to reproduce. > > > > > > Step 1: Configured Multi-Luns in RBOD (DOTHILL) and map to controller > > which is booted with FreeBSD > > > Step 2: Issue the command "camcontrol rescan all" and "camcontrol dev" > > > > > > Expected Result: the command should display all the configured luns > > > > > > Actual Result: Only the first Lun is discovered > > > > > > Note: When we issue explicit scan using "camcontrol rescan > > bus:target:lun", it detects that specific lun. > > > > > > Query: How does FreeBSD detect multi luns ? Driver issue > > XPT_BUS_RESCAN and expect OS should detect both the luns. > > > Is there any limitation associated with multi lun in FreeBSD ? > > > > A couple of questions: > > > > - Do you have change 231716 in your version of the driver? The max_lun > > field of the path inquiry CCB was set to 0, which disabled multiple > > LUN > > scanning. I set it to 8, but in reality it needs to be set to the > > maximum LUN supported by the chip. > > Hi Ken, This is very good information. I was not aware of this max_lun field. > We used FreeBSD-8.2-RELEASE. I can ask test team to verify with latest upstream.(rev 231716) > If you were using 8.2, were you using your own mpslsi driver with it? I'm guessing that your version of the mps driver didn't have the max_lun change. > What about FreeBSD-9-RELEASE ? Is max_luns are set to non-zero. ? The max_lun field needs to be set by the driver. The version of the old mps driver in 9.0 release did set the max_lun field to a non-zero value. But if you were using the mpslsi driver, it probably didn't have that change. > > - What LUN numbers do you have configured on the array? > > Not sure what is correct answer for this. _but_ we have created two luns. And expected to see lun 0 and lun 1. > There is no correct or incorrect answer, but both LUNs should be probed if the max_lun field in the path inquiry CCB returned by the driver is non-zero. What is the maximum LUN number supported by the hardware? You should set the max_lun field to whatever that number is. Ken -- Kenneth Merry ken@FreeBSD.ORG