I just bought a new set of disks, and want to move my primary data store over to the new disks. I created a new pool fine, and now I'm trying to use zfs send -R | zfs receive to transfer the data. Here's the error I got: $ pfexec zfs send -Rpv h...@next | pfexec zfs receive -duvF temp sending from @ to h...@sync receiving full stream of h...@sync into t...@sync sending from @sync to h...@zfs-auto-snap:frequent-2010-04-05-22:00 warning: cannot send 'h...@zfs-auto-snap:frequent-2010-04-05-22:00': no such pool or datasetsending from @zfs-auto-snap:frequent-2010-04-05-22:00 to h...@zfs-auto-snap:frequent-2010-04-06-00:00 warning: cannot send 'h...@zfs-auto-snap:frequent-2010-04-06-00:00': no such pool or dataset sending from @zfs-auto-snap:frequent-2010-04-06-00:00 to h...@zfs-auto-snap:frequent-2010-04-06-11:45 warning: cannot send 'h...@zfs-auto-snap:frequent-2010-04-06-11:45': no such pool or dataset sending from @zfs-auto-snap:frequent-2010-04-06-11:45 to h...@next warning: cannot send 'h...@next': incremental source (@zfs-auto-snap:frequent-2010-04-06-11:45) does not exist cannot receive new filesystem stream: invalid backup stream
This process took about 12 hours to do, so it's frustrating that (apparently) snapshots disappearing causes the replication to fail. Perhaps some sort of locking should be implemented to prevent snapshots that will be needed from being destroyed. In the meantime, I disabled all the zfs/auto-snapshot* services. Should this be enough to prevent the send process from failing again, or are there other steps I should take? Thanks! Will _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
