AHCI and ZFS: root mount error

Alexander Leidinger Alexander at Leidinger.net
Mon Jan 18 11:40:46 UTC 2010


Quoting Wes Morgan <morganw at chemikals.org> (from Sun, 17 Jan 2010  
09:04:16 -0600 (CST)):

> On Sat, 16 Jan 2010, Volodymyr Kostyrko wrote:
>
>> On Sat, 16 Jan 2010 00:29:23 +0100
>> Oliver Brandmueller <ob at 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!

Jumping into the discussion without much knowledge about the initial start...

If this is with 8-stable: the stuff is merged and should work.
If this is with 7-stable: the stuff is merged (by me) since 1-2 weeks.
If this is something else, have a look if the code as displayed at
   http://svn.freebsd.org/viewvc/base?view=revision&revision=200158
is there (after this commit there is nothing else which affects
the ability to find devices).

What may work too is to export the zpool before switching and  
importing it again after switching the storage subsystem.

Bye,
Alexander.

-- 
Do you mean that you not only want a wrong
answer, but a certain wrong answer?
		-- Tobaben

http://www.Leidinger.net    Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org       netchild @ FreeBSD.org  : PGP ID = 72077137


More information about the freebsd-stable mailing list