Date: Sun, 08 Sep 2013 20:11:50 -0700 From: Darren Pilgrim <list_freebsd@bluerosetech.com> To: J David <j.david.lists@gmail.com> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: zfs_enable vs zfs_load in loader.conf (but neither works) Message-ID: <522D3C76.1030705@bluerosetech.com> In-Reply-To: <CABXB=RQoza2YFF81KH_sPksnW5xJuCwd6xaWG4z0TQtS%2BnOs%2Bg@mail.gmail.com> References: <CABXB=RTz6jM=B895Bo6Kp-ZAf2pvTZkm-HfS=PrfX=aMKqjMbw@mail.gmail.com> <522D30C9.8000203@bluerosetech.com> <CABXB=RQoza2YFF81KH_sPksnW5xJuCwd6xaWG4z0TQtS%2BnOs%2Bg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/8/2013 7:52 PM, J David wrote: > On Sun, Sep 8, 2013 at 10:22 PM, Darren Pilgrim > <list_freebsd@bluerosetech.com> wrote: >> Did you build and install new boot blocks? > > Yes. > > Oddly, setting: > > zfs set mountpoint=legacy data/root (plus the appropriate fstab entry) You can use zfs.root.mountfrom="zfs:data/root" in /boot/loader.conf instead of an fstab entry. Mountpoint=legacy is required either way. > instead of > > zfs set mountpoint=/ data/root This only applies to Solaris, IIRC. > seems to produce a bootable system, although it absolutely should not > be necessary to do things that way anymore. I ran into that problem as well. The instructions for root-on-zfs for 9.x (at least as of 9.1) are wrong--you need to use the 8.x-style instructions with mountpoint=legacy for / and, for fresh installs, leaving the pool imported and copying over /boot/zfs/zpool.cache.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?522D3C76.1030705>