Trevor Watson wrote:
> I have had the same problem too, but managed to work around it by
> setting the mountpoint to none before performing the ZFS send. But that
> only works on file-systems you can quiesce.
Yeah, and / is always going to be a bit of a problem ;-)
> How about making a clone o
I have had the same problem too, but managed to work around it by setting the
mountpoint to none before performing the ZFS send. But that only works on
file-systems you can quiesce.
How about making a clone of your snapshot, then set the mounpoint of the clone
to none, take a snapshot of the u
Alan Burlison wrote:
> So how do I tell zfs receive to create the new filesystems in pool3, but
> not actually try to mount them?
This is even more of an issue with ZFS root - as far as I can tell it's
impossible to recursively back up all the filesystems in a root pool
because of this - the r
I have 4 filesystems in a pool that I want to replicate into another
pool, so I've taken snapshots prior to replication:
pool1/home1 14.3G 143G 14.3G /home1
pool1/[EMAIL PROTECTED] 1.57M - 14.3G -
pool1/home2 4.31G 143G 4.31G /home2
pool1/[EMAIL PROTECTED] 0