Date: Sun, 17 Jan 2010 09:04:16 -0600 (CST) From: Wes Morgan <morganw@chemikals.org> To: Volodymyr Kostyrko <c.kworr@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: AHCI and ZFS: root mount error Message-ID: <alpine.BSF.2.00.1001170901050.1524@ibyngvyr> In-Reply-To: <20100116014659.46536463@limbo.lan> References: <7ab0356e1001151213y5536d4cdi1d1759ce28ad546a@mail.gmail.com> <20100115232922.GM45688@e-Gitt.NET> <20100116014659.46536463@limbo.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 16 Jan 2010, Volodymyr Kostyrko wrote: > On Sat, 16 Jan 2010 00:29:23 +0100 > Oliver Brandmueller <ob@e-Gitt.NET> 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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1001170901050.1524>