From owner-freebsd-stable@FreeBSD.ORG Mon Feb 13 11:49:43 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E29D106566C for ; Mon, 13 Feb 2012 11:49:43 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by mx1.freebsd.org (Postfix) with ESMTP id 32C748FC14 for ; Mon, 13 Feb 2012 11:49:42 +0000 (UTC) Received: from omta03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by qmta02.emeryville.ca.mail.comcast.net with comcast id ZPpe1i0010b6N64A2Ppi1D; Mon, 13 Feb 2012 11:49:42 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta03.emeryville.ca.mail.comcast.net with comcast id ZPph1i00r1t3BNj8PPpisv; Mon, 13 Feb 2012 11:49:42 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 7A7EF102C1E; Mon, 13 Feb 2012 03:49:41 -0800 (PST) Date: Mon, 13 Feb 2012 03:49:41 -0800 From: Jeremy Chadwick To: Johan Hendriks Message-ID: <20120213114941.GA71078@icarus.home.lan> References: <20120202191105.GA55719@nargothrond.kdm.org> <4F38E00B.2020408@gmail.com> <4F38EFE2.7010905@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F38EFE2.7010905@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable , "Desai, Kashyap" Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2012 11:49:43 -0000 On Mon, Feb 13, 2012 at 12:11:30PM +0100, Johan Hendriks wrote: > Ok so it is not the mps driver who does the naming but cam, and that > also has changed on 9.0 Stable. > Well i use gpart labels for the pool, so i can use the gpart labels > to yank the right disk. > But it would be nicer if there was some kind of logic in the > numbering of the devices. "Wire them down" in FreeBSD using loader.conf variables and this issue will cease to be a problem. Example is below, despite being for SATA with AHCI -- really doesn't matter, just change the appropriate bits and it should be fine for you. # "Wire down" device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # hint.scbus.0.at="ahcich0" hint.scbus.1.at="ahcich1" hint.scbus.2.at="ahcich2" hint.scbus.3.at="ahcich3" hint.scbus.4.at="ahcich4" hint.scbus.5.at="ahcich5" hint.ada.0.at="scbus0" hint.ada.1.at="scbus1" hint.ada.2.at="scbus2" hint.ada.3.at="scbus3" hint.ada.4.at="scbus4" hint.ada.5.at="scbus5" -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |