From owner-freebsd-fs@FreeBSD.ORG Mon Sep 9 17:15:19 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2860EADE for ; Mon, 9 Sep 2013 17:15:19 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EE10C2648 for ; Mon, 9 Sep 2013 17:15:18 +0000 (UTC) Received: by mail-ie0-f179.google.com with SMTP id m16so10614054ieq.24 for ; Mon, 09 Sep 2013 10:15:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=T9qhDGRsSUzQNlICMJsZdtSswV3AteZ8NgA6myIaEyc=; b=sJOjugUk0U7B5jDJpXDQwvqQCw6SmJVFDMueCU+OieA40QeQFhGkaWk1vGHBzuQcKA CAyEFL1XtesnbK9DvTNtErQNRdQt5akN5mXPLbFZeO7Xn2vREwPKSaIRmrJzNwTNsTmf Uqxtj/vonLoEYQ0O6dLDRsrGzGUBMd9g4wjmZCWUz3RSQzxa/S1VDZyGAMnCczwm14UB N5z/+QhO30nuzTokU8aNPXnkcAcFpgWrNBoEttORiAhvQtNuVGGWzlrkPAtJ7dt/H8JI X27wSHEhtBuNMPZScY0ZFu2VvuqkmdDFEv1rHJEQ66Aubkic+BwjQEU9Ij2RPip/MvC2 uqEQ== MIME-Version: 1.0 X-Received: by 10.42.53.18 with SMTP id l18mr33279icg.78.1378746917632; Mon, 09 Sep 2013 10:15:17 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.43.157.8 with HTTP; Mon, 9 Sep 2013 10:15:17 -0700 (PDT) In-Reply-To: References: <522D67DB.7060404@infracaninophile.co.uk> Date: Mon, 9 Sep 2013 13:15:17 -0400 X-Google-Sender-Auth: X3ONUog59x48KAhpOLeCmDbJjng Message-ID: Subject: Re: zfs_enable vs zfs_load in loader.conf (but neither works) From: J David To: krad Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Sep 2013 17:15:19 -0000 On Mon, Sep 9, 2013 at 8:55 AM, krad wrote: > you will find without 'zfs_enable="YES" ' set a lot of the zfs datasets > might not get mounted Matthew has the same understanding of this that I do: zfs_load goes in loader.conf and zfs_enable goes in rc.conf. zfs_load causes the loader to load zfs.ko and opensolaris.ko so that the kernel can access the zpool (e.g. to mount the root filesystem) after /boot/zfsloader finishes. zfs_enable in rc.conf activates the /etc/rc.d/zfs and /etc/rc.d/zvol scripts. (And tweaks mountd on nfs servers.) There are several online ZFS-root recipies that say differently (mainly that using zfs_load has been replaced by zfs_enable in loader.conf), but I haven't found any authoritative references that support that. Have you? (Also, it doesn't work in testing; the two .ko's aren't loaded if zfs_load is not present.) In the absence of new info, that seems like the right way to do it. Things get sticky when it comes to establishing the ZFS root filesystem. There are at least four ways to go about it: 1) Set vfs.root.mountfrom="zfs:data/root" in loader.conf. 2) Run "zpool set bootfs=data/root data" on the pool. 3) Run "zfs set mountpoint=/ data/root" on the root filesystem. 4) Run "zfs set mountpoint=legacy data/root" on the root filesystem and an /etc/fstab entry. Unfortunately, some of these are not sufficient by themselves, or they don't work at all. So the question is, for 9.2, which (combination of?) these is the authoritatively correct way to identify the ZFS root filesystem? And, for the sake of release engineering, how does 9.2 differ from 9.1 in this regard? Thanks!