From owner-freebsd-fs@FreeBSD.ORG  Sun Dec 25 20:22:12 2011
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 766501065672
	for <freebsd-fs@freebsd.org>; Sun, 25 Dec 2011 20:22:12 +0000 (UTC)
	(envelope-from artemb@gmail.com)
Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com
	[209.85.213.182])
	by mx1.freebsd.org (Postfix) with ESMTP id 312D88FC0A
	for <freebsd-fs@freebsd.org>; Sun, 25 Dec 2011 20:22:11 +0000 (UTC)
Received: by yenl9 with SMTP id l9so7514241yen.13
	for <freebsd-fs@freebsd.org>; Sun, 25 Dec 2011 12:22:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=wh2hqnAZqJU4Ds1yMzDHpjNROWT/mOl4/lc9LH8M9M8=;
	b=d3L9rswscHx1K78X/RSRuIIY9Bc/45fgJCx0O9aVtD+N9BpvFWs+fNWXTohzJAI5qU
	IUU+YwtKyNOsh3a5hi1P5XB4xjnb9wJQWbe1nOqw1cmCp4cNns0fWUj5ecK3rGeoqK6T
	WTuPznNN1P6XKindIGBzwiDPPotdN85/SNveU=
MIME-Version: 1.0
Received: by 10.236.131.97 with SMTP id l61mr30675941yhi.52.1324844531514;
	Sun, 25 Dec 2011 12:22:11 -0800 (PST)
Sender: artemb@gmail.com
Received: by 10.147.52.27 with HTTP; Sun, 25 Dec 2011 12:22:11 -0800 (PST)
In-Reply-To: <jd7up6$i4g$1@dough.gmane.org>
References: <20111225102719.GA44906@tolstoy.tols.org>
	<jd76dj$foe$1@dough.gmane.org>
	<CAM-i3iiH34rCAQZJvXn37jXWzq0E5++N8nK441yFLTsWQfOuCw@mail.gmail.com>
	<jd7up6$i4g$1@dough.gmane.org>
Date: Sun, 25 Dec 2011 12:22:11 -0800
X-Google-Sender-Auth: RUj5ctRhG2UYnrjr7SqJAvjZt3U
Message-ID: <CAFqOu6jsMZJvr88zdvZUdnLSRk9e6OPpDgi+KbjvfLHaOmn41A@mail.gmail.com>
From: Artem Belevich <art@freebsd.org>
To: Johannes Totz <johannes@jo-t.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-fs@freebsd.org
Subject: Re: Restoring received properties on a received filesystem.
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Sun, 25 Dec 2011 20:22:12 -0000

On Sun, Dec 25, 2011 at 11:49 AM, Johannes Totz <johannes@jo-t.de> wrote:
> On 25/12/2011 13:02, claudiu vasadi wrote:
>>
>> On Sun, Dec 25, 2011 at 1:54 PM, Johannes Totz<johannes@jo-t.de> =A0wrot=
e:
>>
>> Check out zfs receive -u, it doesn't mount the receiving filesystem. zpo=
ol
>>>
>>> import -N doesn't mount your importing backup-pool.
>>>
>>>
>> True, it doesn't, but upon reboot, since the received datasets keep thei=
r
>> properties, they will be mounted (and this has the risk of potentially
>> overwriting an exiting mountpoint).
>
>
> Good point! Haven't thought about reboot, I always export my backup pool
> when I'm done with send-receive.
> Could be worked around, I guess, by disabling cache file entry and manual=
ly
> importing it from some random script...

Perhaps "zpool import/create -R /foo" (or "-o altroot=3Dfoo,
cachefile=3Dnone") is what you're looking for. It effectively gives your
pool its own name space under /foo and it does not record any info
about it in zpool cache, so on reboot the pool should remain
unimported.

--Artem