From owner-freebsd-fs@FreeBSD.ORG Mon Jan 5 21:22:03 2015 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 71EC4988 for ; Mon, 5 Jan 2015 21:22:03 +0000 (UTC) Received: from thyme.infocus-llc.com (thyme.infocus-llc.com [199.15.120.10]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 45FD064230 for ; Mon, 5 Jan 2015 21:22:03 +0000 (UTC) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id 94A2637B62B; Mon, 5 Jan 2015 15:21:56 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3kGVCS0BXDz2Zp; Mon, 5 Jan 2015 15:21:56 -0600 (CST) Date: Mon, 5 Jan 2015 15:21:55 -0600 From: "Matthew D. Fuller" To: Tim Gustafson Subject: Re: ZFS Send / Receive Recursively Without Properties Message-ID: <20150105212155.GI1937@over-yonder.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.23-fullermd.4 (2014-03-12) X-Virus-Scanned: clamav-milter 0.98.5 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2015 21:22:03 -0000 On Mon, Jan 05, 2015 at 11:05:55AM -0800 I heard the voice of Tim Gustafson, and lo! it spake thus: > > This works well, except that it sets the mountpoints on server "B" > server's copy of the file systems to whatever they were on the > source system, which overwrites server "B"'s root file system when > we send the root file system from server "A". I've run into this a time or two. I was actually thinking recently it might be nice to have a property on a filesystem similar to the zpool-level altroot, specifically for cases like this. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.