From owner-freebsd-fs@FreeBSD.ORG  Mon Sep  9 03:11:57 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 7DF54152;
 Mon,  9 Sep 2013 03:11:57 +0000 (UTC)
 (envelope-from list_freebsd@bluerosetech.com)
Received: from yoshi.bluerosetech.com (yoshi.bluerosetech.com
 [IPv6:2607:f2f8:a450::66])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 64B232086;
 Mon,  9 Sep 2013 03:11:57 +0000 (UTC)
Received: from chombo.houseloki.net (unknown
 [IPv6:2001:558:6025:2d:68f0:67e3:f35d:f840])
 by yoshi.bluerosetech.com (Postfix) with ESMTPSA id A9D07E6040;
 Sun,  8 Sep 2013 20:11:53 -0700 (PDT)
Received: from [127.0.0.1] (ivy.houseloki.net [10.9.70.20])
 by chombo.houseloki.net (Postfix) with ESMTPSA id 78539256;
 Sun,  8 Sep 2013 20:11:52 -0700 (PDT)
Message-ID: <522D3C76.1030705@bluerosetech.com>
Date: Sun, 08 Sep 2013 20:11:50 -0700
From: Darren Pilgrim <list_freebsd@bluerosetech.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: J David <j.david.lists@gmail.com>
Subject: Re: zfs_enable vs zfs_load in loader.conf (but neither works)
References: <CABXB=RTz6jM=B895Bo6Kp-ZAf2pvTZkm-HfS=PrfX=aMKqjMbw@mail.gmail.com>
 <522D30C9.8000203@bluerosetech.com>
 <CABXB=RQoza2YFF81KH_sPksnW5xJuCwd6xaWG4z0TQtS+nOs+g@mail.gmail.com>
In-Reply-To: <CABXB=RQoza2YFF81KH_sPksnW5xJuCwd6xaWG4z0TQtS+nOs+g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>,
 freebsd-stable <freebsd-stable@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2013 03:11:57 -0000

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.