On January 30, 2009 1:09:49 PM -0500 Mark J Musante <mmusante at
east.sun.com>
wrote:
On Fri, 30 Jan 2009, Frank Cusack wrote:
so, is there a way to tell zfs not to perform the mounts for data2? or
another way i can replicate the pool on the same host, without exporting
the original pool?
There is not a way to do that currently, but I know it's coming down the
road.
just for closure, a likely solution (seems correct, but i am unable to
test just now) was presented in another thread. i note the answer here
so that a search which finds this thread has both the question and answer
in the same place.
On January 31, 2009 10:57:11 AM +0100 Kees Nuyt <k.nuyt at zonnet.nl>
wrote:
That property is called "canmount".
man zfs
/canmount
i didn't test, but it seems that setting canmount to noauto, replicating,
then changing canmount back to on, would do the trick.
It turns out this doesn't work for datasets that are mounted in the
global zone that you can't unmount.
Setting the canmount property to 'noauto' has the side effect (why?) of
immediately unmounting, and failing if it can't do so. For datasets
which are zoned, if you are running the 'zfs set' in the global zone,
the dataset remains mounted in the zone. But for datasets mounted in
the global zone, e.g. being served via NFS, the 'zfs set' fails.
Funny though, I wrote the above and tested a few more times, and now
I do have one of my home directories' canmount property set to 'noauto',
and I can no longer change it back to 'on'. How it got set to 'noauto'
is a mystery as it was never unmounted during the brief time I have
been composing this email, and I was consistently getting an error
message from zfs about it being in use.
-frank
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
