zfs discuss - Jun 2009 - zfs replication via zfs send/recv dead after 2009.06 update

Hello,

I had two thumpers replicating via zfs incremental send/recv croned over ssh
with blowfish eneabled under 2008.11. The 2009.06 update nuked blowfish and my
cronjob failed in then deleted the snapshots on the master and slave servers.

now if I try to run the job I get the error:

cannot receive incremental stream: most recent snapshot of slave/slavezfsvol
does not
match incremental source

Is there any way to recover from this error without re-syncing the zfs volumes
from scratch?
Here is the cron job 

/root/zync dataPool/wigler root at bhstore11 dataPool/wiglerBHStore11

Here is the salient cron script....

ENCRYPT="-c blowfish"
DATE=`/usr/gnu/bin/date +%s`
HOSTNAME=`hostname`

       # Datafile is found, creating incr.
        echo "Incremental started at `date`"
        zfs snapshot ${1}@${DATE}
        zfs send  -i  ${1}@`cat /root/run/zynk` ${1}@${DATE} | ssh $ENCRYPT ${2}
zfs recv -F  ${3}
        zfs destroy ${1}@`cat /root/run/zynk`
        ssh ${2} zfs destroy ${3}@`cat /root/run/zynk`
        echo ${DATE} > /root/run/zynk
        echo "Incremental complete at `date`"



Is there is a way to force a re-sync of the zfs volumes, as there has been no
change in data on the master volume hat needs to be synced to the slave server?

Thanks,

Dan
-- 
This message posted from opensolaris.org

I had the same issue and did the following;

   * disabled the auto-snapshot services (enabled by default I think)
   * removed all auto-snapshots on the filesystems I wanted to send that were
between the two snapshots I was referring to (start and end snapshot of the
incremental)

Then I could do the send and receive as per normal.

Not sure if that will help you also, but thought it was worth putting up here.

Cheers,

Sally.
-- 
This message posted from opensolaris.org