From owner-freebsd-fs@FreeBSD.ORG Tue Sep 10 11:23:32 2013 Return-Path: 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 E7F77D94 for ; Tue, 10 Sep 2013 11:23:32 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-vc0-x233.google.com (mail-vc0-x233.google.com [IPv6:2607:f8b0:400c: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 A494D2055 for ; Tue, 10 Sep 2013 11:23:32 +0000 (UTC) Received: by mail-vc0-f179.google.com with SMTP id ht10so4793643vcb.24 for ; Tue, 10 Sep 2013 04:23:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TlvxzjXpf0WYnuVM8X2gi0ha5fx/RjWoce5lboJr5g4=; b=NHFaUXcYg5Z/67NMBRegmjh+cr5goQSjWqPJVG+d+kDFn8QESw6h9pF6eI0tHgbsf9 vwvLsh30NoBJBAmrLZ+o8Gxxn1MedRqUJxMu34VGS42Fz0dWvOQPVYWD6ymcVEw3fAcE K8saAM1+iTdsIikKNtPUyVM2uSB+SLJuWdWTBPWmwPcy5YmYg7yFOLzhbinkVrt/LjPh tjudj6+qgXkG8RD8GNyawVaCceN4NBJMG4YGny5adzQUdtFlhhuR13pX3UyVyxYLKoxd uNFhLkyi3yNZJmADeLKlTClNFR+i/N1OuKeTUqiFFNL6S55T0vSXFqWtms+JxKz0uCsF OidQ== MIME-Version: 1.0 X-Received: by 10.58.118.130 with SMTP id km2mr22203191veb.0.1378812211877; Tue, 10 Sep 2013 04:23:31 -0700 (PDT) Received: by 10.221.21.70 with HTTP; Tue, 10 Sep 2013 04:23:31 -0700 (PDT) In-Reply-To: References: <522D67DB.7060404@infracaninophile.co.uk> <522E07B1.5030205@platinum.linux.pl> Date: Tue, 10 Sep 2013 12:23:31 +0100 Message-ID: Subject: Re: zfs_enable vs zfs_load in loader.conf (but neither works) From: krad To: J David Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Tue, 10 Sep 2013 11:23:33 -0000 you could probably play with the canmount property though On 10 September 2013 12:22, krad wrote: > "Using mountpoint=legacy seems a little conceptually challenged, > especially given that the description of a legacy mount is:" > > not really as what is one of the 1st things the kernel does after it is > loaded with all its modules? It looks to mount the root filesystem. This is > something that happens outside zfs's control from what I understand so is a > legacy mount rather than a zfs controlled one. The bootfs property of a > pool is actually used by the zfsloader to locate the file system the > loader.conf etc is on. The loader may or may not choose to pass this > parameter through to the kernels environment, and its totally possible to > have / set to a different dataset than the bootfs option. > > "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.)" > > Its doesn't get mounted as its legacy, ie you have to mount the dataset > manually where ever you see fit > > "And, finally, what would have to change to support a ZFS root filesystem > set as mountpoint=/ instead of mountpoint=legacy ?" > > Why would you want to? > > > > > On 9 September 2013 19:46, J David wrote: > >> 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! >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> > >