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 reason being that one filesystem in the root pool will *always* be mounted as /, and when zfs receive creates the copied filesystem for / it also tries to mount it as /, and fails. NAME USED AVAIL REFER MOUNTPOINT solaris 6.89G 12.7G 30K /solaris solaris/ROOT 6.88G 12.7G 18K /solaris/ROOT solaris/ROOT/onnv_92 65.8M 12.7G 3.98G / solaris/ROOT/onnv_94 2.76G 12.7G 3.99G / solaris/ROOT/test 4.06G 12.7G 3.98G / solaris/ROOT/[EMAIL PROTECTED] 296K - 3.98G - # zfs snapshot -r [EMAIL PROTECTED] # zfs create -o mountpoint=none -o canmount=off backup/fire/solaris # zfs send -R [EMAIL PROTECTED] | zfs receive -Fdv backup/fire/solaris receiving full stream of [EMAIL PROTECTED] into backup/fire/[EMAIL PROTECTED] received 30.5KB stream in 1 seconds (30.5KB/sec) receiving full stream of solaris/[EMAIL PROTECTED] into backup/fire/solaris/[EMAIL PROTECTED] received 13.6KB stream in 1 seconds (13.6KB/sec) receiving full stream of solaris/ROOT/[EMAIL PROTECTED] into backup/fire/solaris/ROOT/[EMAIL PROTECTED] cannot mount '/': directory is not empty Shouldn't there be a flag (-n?) for use with receive -R that prevents the newly-copied filesystems from being mounted? Or am I missing something obvious? -- Alan Burlison -- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
