From owner-freebsd-current@FreeBSD.ORG Thu Apr 21 22:35:38 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2649A1065673; Thu, 21 Apr 2011 22:35:38 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id D42BC8FC16; Thu, 21 Apr 2011 22:35:37 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.4/8.14.4/NETPLEX) with ESMTP id p3LMZaIA007154; Thu, 21 Apr 2011 18:35:36 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.2.6 (mail.netplex.net [204.213.176.10]); Thu, 21 Apr 2011 18:35:36 -0400 (EDT) Date: Thu, 21 Apr 2011 18:35:36 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Arnaud Lacombe In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Garrett Cooper , Alexander Motin , FreeBSD-Current Subject: Re: Devices numbering [Was Re: Switch from legacy ata(4) to CAM-based ATA] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2011 22:35:38 -0000 On Thu, 21 Apr 2011, Arnaud Lacombe wrote: > Hi, > > On Thu, Apr 21, 2011 at 1:31 PM, Garrett Cooper wrote: >> Although this may not be a list of fixable issues, here are some observations (in part with the new geom raid infrastructure): >> 1. Channels are no longer fixed of course because ata uses cam now, and I believe that device numbering is done based on probe ordering. This is fun to work with when dealing with appliances or configurations that require deterministic probe and mount, especially when drives fail, go missing, etc, but can be hacked around in device.hints. This is why it would be nice for geom labels to work in a sane manner. > Out of context, but the same issue appear with network interfaces. If > you're got 6 networks interface and the 3rd chip die, the 3 last get a > bad numbering. I am not sure it is fixable by any device.hints. > > The Linux' world has the same issue (well, worse actually, as all > interfaces uses the same 'eth' name). RedHat has been/will be > introducing "Consistent Network Device Naming"[0,1] in Fedora 15, > which may be an interesting move. > > - Arnaud > > [0]: http://domsch.com/linux/lpc2010/lpc2010-network-device-naming.pdf > [1]: http://domsch.com/blog/?p=455 Solaris /etc/path_to_inst anyone? }B-> -- DE