Date: Sun, 25 Dec 2011 12:22:11 -0800 From: Artem Belevich <art@freebsd.org> To: Johannes Totz <johannes@jo-t.de> Cc: freebsd-fs@freebsd.org Subject: Re: Restoring received properties on a received filesystem. Message-ID: <CAFqOu6jsMZJvr88zdvZUdnLSRk9e6OPpDgi%2BKbjvfLHaOmn41A@mail.gmail.com> In-Reply-To: <jd7up6$i4g$1@dough.gmane.org> References: <20111225102719.GA44906@tolstoy.tols.org> <jd76dj$foe$1@dough.gmane.org> <CAM-i3iiH34rCAQZJvXn37jXWzq0E5%2B%2BN8nK441yFLTsWQfOuCw@mail.gmail.com> <jd7up6$i4g$1@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFqOu6jsMZJvr88zdvZUdnLSRk9e6OPpDgi%2BKbjvfLHaOmn41A>