From owner-freebsd-fs@FreeBSD.ORG Tue Sep 10 11:22:45 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 785C18B5 for ; Tue, 10 Sep 2013 11:22:45 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-ve0-x22b.google.com (mail-ve0-x22b.google.com [IPv6:2607:f8b0:400c:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 356C42F6D for ; Tue, 10 Sep 2013 11:22:45 +0000 (UTC) Received: by mail-ve0-f171.google.com with SMTP id pa12so5100398veb.16 for ; Tue, 10 Sep 2013 04:22:44 -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=p2O8A5vfobea1mm5QQcmWm9vP58/7AK/BCeS91F7BHI=; b=0QmXmZHKVVJVo9ayUuXX3PgJVKTPunGam2eT4u5VzpVdypNYPJE1Cg+QPSremL0hBR Vx0STQoNq+2TTxAl6ugXqsTua05t7/C8InGl4FmJ7BKbz8xzFKytiNUvXzjn+KIZgIga pVePsGo4aFtBrAqOtypu9MGUd9QIkXmaYy6yeAudqR2ZsHrt83+K3T9eYvb5bhuhB2C5 MDmjTyNG9V56aJiXJpr85bIZ/s9jlhGnPtFFJm9X98jsL7qJiCGJx1UjtiFVyIG+33WK 492JpMFbxWENPObkpcqXg/g4renJ3qCBVfouh3LRBAtQdVUyLX5ZbUMO2Mhd6u4M3AV8 anJg== MIME-Version: 1.0 X-Received: by 10.220.181.136 with SMTP id by8mr22932543vcb.11.1378812164412; Tue, 10 Sep 2013 04:22:44 -0700 (PDT) Received: by 10.221.21.70 with HTTP; Tue, 10 Sep 2013 04:22:44 -0700 (PDT) In-Reply-To: References: <522D67DB.7060404@infracaninophile.co.uk> <522E07B1.5030205@platinum.linux.pl> Date: Tue, 10 Sep 2013 12:22:44 +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:22:45 -0000 "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" >