On Sat, Jan 23, 2010 at 8:44 AM, Fletcher Cocquyt <fcocq...@stanford.edu> wrote: > Fletcher Cocquyt <fcocquyt <at> stanford.edu> writes: > > >> I found this script for replicating zfs data: >> > http://www.infrageeks.com/groups/infrageeks/wiki/8fb35/zfs_autoreplicate_script.html >> >> - I am testing it out in the lab with b129. >> It error-ed out the first run with some syntax error about the send component >> (recursive needed?) >> > ..snip.. >> >> How do I clear the lock - I have not been able to find documentation on >> this... >> >> thanks! >> > > Hi, as one helpful user pointed out, the lock is not from ZFS, but an > attribute > set by the script to prevent contention (multiple replications etc). > I used zfs get/set to clear the attribute and I was able to replicate the > initial dataset - still working on the incrementals! > > thanks! > > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >
As the person who put in the original code for the ZFS lock/depend checks, the script is relatively simple. Seems Infrageeks added some better documentation which is very helpful. You'll want to make sure your remote side doesn't differ, ie. has the same current snapshots as the sender side. If the replication fails for some reason, "unlock" both sides with 'zfs set'. What problems are your experiencing with incrementals? -- Brent Jones br...@servuhome.net _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
