Multiple ZFS pools and booting

[Ronald Klop]

Shouldn't you set the boot device in /boot/loader.conf?
I have this line:
vfs.root.mountfrom="zfs:zroot"

Ronald.

On Fri, 14 Jan 2011 14:31:11 +0100, Marcus Müller  
<znek at mulle-kybernetik.com> wrote:

> Hi all,
>
> I have a single harddrive with GPT partitioning:
>
> root at muller:(~)# gpart show
> =>       34  234441581  ad10  GPT  (112G)
>          34        128     1  freebsd-boot  (64K)
>         162    8388608     2  freebsd-swap  (4.0G)
>     8388770   10485760     3  freebsd-zfs  (5.0G)
>    18874530   10485760     4  freebsd-zfs  (5.0G)
>    29360290  102540662     5  freebsd-zfs  (49G)
>   131900952  102540662     6  freebsd-zfs  (49G)
>   234441614          1        - free -  (512B)
>
> ad10p3/ad10p4 (tank) and ad10p5/ad10p6 (muller) are two mirror zpools.  
> The root filesystem currently resides on tank.
>
> I wanted to migrate the root filesystem from tank to muller by changing  
> the mountpoints accordingly and resetting the bootfs zpool propery on  
> tank like this:
>
> root at muller:(~)# zpool get bootfs muller
> NAME    PROPERTY  VALUE                   SOURCE
> muller  bootfs    muller/roots/8-current  local
> root at muller:(~)# zpool set bootfs= tank
> root at muller:(~)# zpool get bootfs tank
> NAME  PROPERTY  VALUE   SOURCE
> tank  bootfs    -       default
>
> But when I reboot, BTX loader tries to access tank:/boot/kernel/kernel.
>
> Why does the loader care about tank at all, after I "removed" the bootfs  
> property?
> Do I have to export tank before I reboot?
> How do I tell the loader to just care about muller for booting?
>
> Thanks for any help in advance,
>
>   Marcus