From owner-freebsd-questions@FreeBSD.ORG Fri Oct 26 23:05:48 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E986BD59 for ; Fri, 26 Oct 2012 23:05:48 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id A1ADE8FC08 for ; Fri, 26 Oct 2012 23:05:48 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q9QN5iKo062881; Fri, 26 Oct 2012 17:05:44 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q9QN5hwt062878; Fri, 26 Oct 2012 17:05:43 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 26 Oct 2012 17:05:43 -0600 (MDT) From: Warren Block To: Jeremy Chadwick Subject: Re: ata controller problem In-Reply-To: <20121026163338.GA32286@icarus.home.lan> Message-ID: References: <20121026163338.GA32286@icarus.home.lan> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Fri, 26 Oct 2012 17:05:44 -0600 (MDT) Cc: freebsd@edvax.de, freebsd-questions@freebsd.org, schmidt@ze.tum.de X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 23:05:49 -0000 On Fri, 26 Oct 2012, Jeremy Chadwick wrote: > Regarding this: > > http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html > > No no NO *NO*! > > I wish people would stop recommending this utter garbage. There is > absolutely no justification behind using the highly convoluted labelling > mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) > different "label" mechanisms which do nothing but confuse the user, or > cause other oddities/complexities. Good grief, there is so much hard > evidence on the mailing lists over the past 5 (maybe even 7?) years > talking about the utter mess that is filesystem/device/geom/blahblah > labels that to recommend this is borderline insane. Hmm. Six months to April 1? Seriously, labels provide a simple, relocatable identification mechanism that works across machines. If someone finds them confusing, it can be cleared up easily: use GPT labels when possible, otherwise use filesystem labels or glabel. > The proper way to solve this problem is to user /boot/loader.conf > tie-downs to assign each disk to each individual controllers' device > number (e.g. ada0 --> scbus0 --> ahcich0, or whatever you want). Please > note I said ahcichX, not ahciX. Different things. Labels work on different machines or controllers without added configuration, and stay with the partition or filesystem. Your static config appears to not share those properties.