From owner-freebsd-fs@FreeBSD.ORG Mon Sep 9 18:46:46 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 B24369E7 for ; Mon, 9 Sep 2013 18:46:46 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8346E2C30 for ; Mon, 9 Sep 2013 18:46:46 +0000 (UTC) Received: by mail-ie0-f181.google.com with SMTP id y16so8144518ieg.26 for ; Mon, 09 Sep 2013 11:46:46 -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=TT1Wra7/iFwerecfwiMgMBEAdArTzcWmyd1fmCbmVFA=; b=TvIb2tahxfCeMr6RaMYcaRbu49JuoGCa0WDu/sxCjho+2d5vGrYlM+KGg5P7kq4TqU pmDpX03a9o+H6t2b8qEGCA77TLf1xG2CQyP089/IKD9ZdwTLnBIM8KD8ny7w7EMsoIii Rua0AdNy2LZLOJj8Tq4weeNzTlpPAlf+egm+/BWtBs1QyKYqP2DR6loj2TaAn/6N44te cdxrDcTlHuM+5+N7NNky9xR9nw7wl8uk4Anj+ZaEoTD30AQ/ooGS7g68He662/Lfg1qa Mg8yOPZNiXZmRholVhTniJ8JvfDMNjj740BPLxq48PKwWlhS2g3an71bUVRAIrIfVo48 y1Og== MIME-Version: 1.0 X-Received: by 10.50.20.195 with SMTP id p3mr9205909ige.26.1378752406064; Mon, 09 Sep 2013 11:46:46 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.43.157.8 with HTTP; Mon, 9 Sep 2013 11:46:45 -0700 (PDT) In-Reply-To: <522E07B1.5030205@platinum.linux.pl> References: <522D67DB.7060404@infracaninophile.co.uk> <522E07B1.5030205@platinum.linux.pl> Date: Mon, 9 Sep 2013 14:46:45 -0400 X-Google-Sender-Auth: mg9GoBzDNMAv4PrwYOIovvCeoPY Message-ID: Subject: Re: zfs_enable vs zfs_load in loader.conf (but neither works) From: J David To: Adam Nowacki Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-fs@freebsd.org" 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 18:46:46 -0000 On Mon, Sep 9, 2013 at 1:38 PM, Adam Nowacki wrote: > zfs set mountpoint=legacy data/root > together with > zpool set bootfs=data/root data This does appear to work, thanks. So the key steps seem to be: 1) zfs_load="YES" in loader.conf 2) zfs_enable="YES" in rc.conf 3) Set bootfs=data/root in the zpool. 4) Set mountpoint=legacy on the root fs Using mountpoint=legacy seems a little conceptually challenged, especially given that the description of a legacy mount is: "If a file system's mount point is set to legacy, ZFS makes no attempt to manage the file system, and the administrator is responsible for mounting and unmounting the file system." Is this bending things to claim setting bootfs is adequate example of the administrator's responsibility to mount the file system? (Even though that is clearly also part of ZFS.) How does mountpoint=legacy interact with importing the pool on another system, or from a LiveCD, with " -o altroot=/mnt " ? (A case where mountpoint=/ works perfectly.) And, finally, what would have to change to support a ZFS root filesystem set as mountpoint=/ instead of mountpoint=legacy ? Thanks!