From owner-freebsd-stable@FreeBSD.ORG Sun Jan 17 15:04:22 2010 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 62570106566B for ; Sun, 17 Jan 2010 15:04:22 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id C148A8FC13 for ; Sun, 17 Jan 2010 15:04:21 +0000 (UTC) Received: from volatile.chemikals.org (adsl-67-242-76.shv.bellsouth.net [98.67.242.76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 72132A223D4A; Sun, 17 Jan 2010 09:04:20 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id o0HF4GfM070345; Sun, 17 Jan 2010 09:04:16 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Sun, 17 Jan 2010 09:04:16 -0600 (CST) From: Wes Morgan X-X-Sender: morganw@volatile To: Volodymyr Kostyrko In-Reply-To: <20100116014659.46536463@limbo.lan> Message-ID: References: <7ab0356e1001151213y5536d4cdi1d1759ce28ad546a@mail.gmail.com> <20100115232922.GM45688@e-Gitt.NET> <20100116014659.46536463@limbo.lan> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: clamav-milter 0.95.2 at warped X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: AHCI and ZFS: root mount error 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: Sun, 17 Jan 2010 15:04:22 -0000 On Sat, 16 Jan 2010, Volodymyr Kostyrko wrote: > On Sat, 16 Jan 2010 00:29:23 +0100 > Oliver Brandmueller wrote: > > > Check with "zpool status" if your zpool refers to diskslices like > > "ad0s1". I use gpt have setup the ZFS mirror to refer to gptids: > > > > pool: silver > > state: ONLINE > > scrub: none requested > > config: > > > > NAME STATE READ WRITE CKSUM > > silver ONLINE 0 0 0 > > mirror ONLINE 0 0 0 > > gptid/9e68d234-f306-11de-a0c4-0002b3b6e838 ONLINE 0 0 0 > > gptid/a025b88c-f306-11de-a0c4-0002b3b6e838 ONLINE 0 0 0 > > > > With that kind of configuration I can switch back and forth between > > using ATA_CAM or using traditional ATA drivers. Since you're not using > > GPT I gues you can use geom labels to do more or less the same thing. > > > > In short: use labels, nut device names. Saves headaches in many cases. > > ZFS actually can find disks without any glabel help. I have one server > which I have moved recently to ahci and nothing changes for me. ZFS > silently accepted new provider names and continue working as usual. > Agreed, I experienced the same thing here when I moved to AHCI. I think pjd committed some changes in the last few months that greatly improved the ability of zfs to find devices by uuid. Using glabel or gptid's with zfs is highly overrated IMO!