From owner-freebsd-fs@FreeBSD.ORG  Tue Jan 22 13:41:19 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])
 by hub.freebsd.org (Postfix) with ESMTP id 8A72EB27
 for <freebsd-fs@FreeBSD.org>; Tue, 22 Jan 2013 13:41:19 +0000 (UTC)
 (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id B75CB6F4
 for <freebsd-fs@FreeBSD.org>; Tue, 22 Jan 2013 13:41:18 +0000 (UTC)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
 [212.40.38.101])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA29553;
 Tue, 22 Jan 2013 15:41:14 +0200 (EET) (envelope-from avg@FreeBSD.org)
Message-ID: <50FE96F9.6000900@FreeBSD.org>
Date: Tue, 22 Jan 2013 15:41:13 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130113 Thunderbird/17.0.2
MIME-Version: 1.0
To: Borja Marcos <borjam@sarenet.es>
Subject: Re: RFC: Suggesting ZFS "best practices" in FreeBSD
References: <314B600D-E8E6-4300-B60F-33D5FA5A39CF@sarenet.es>
In-Reply-To: <314B600D-E8E6-4300-B60F-33D5FA5A39CF@sarenet.es>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: FreeBSD Filesystems <freebsd-fs@FreeBSD.org>,
 Scott Long <scottl@samsco.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: Tue, 22 Jan 2013 13:41:19 -0000

on 22/01/2013 13:03 Borja Marcos said the following:
> pool/root pool/root/var pool/root/usr pool/root/tmp
> 
> Why pool/root instead of simply "pool"? Because it's easier to understand,
> snapshot, send/receive, etc. Why in a hierarchy? Because, if needed, it's
> possible to snapshot the whole "system" tree atomically.

I recommend placing "/" into pool/ROOT/<current-name>.
That would very useful for boot environments (BEs - use them!).

> I also set the mountpoint of the "system" tree as legacy, and rely on
> /etc/fstab.

I do place anything for ZFS into fstab.
Nor I use vfs.root.mountfrom loader variable.
I depend on the boot and kernel code doing the right thing based on pool's bootfs
property.

> Why? In order to avoid an accidental "auto mount"  of critical
> filesystems in case, for example, I boot off a pendrive in order to tinker.

Not sure what you mean, if you don't import the pool nothing gets mounted.
If you remember to use import -R then everything gets mounted in controlled places.

-- 
Andriy Gapon