The problem is not with how the replication is done. The locking happens
during the basic zfs operations.
We noticed:
on server2 (which is quite busy serving maildirs) we did
zfs create tank/newfs
rsync 4GB from someotherserver to /tank/newfs
zfs destroy tank/newfs
Destroying newfs took more
Sorry i'm not able to provide more insight but I thought some of the
concepts in this article might help you, as well as Mike's replication
script, also available on this page:
http://blog.laspina.ca/ubiquitous/provisioning_disaster_recovery_with_zfs
You also might want to look at InfraGeeks auto-
Hello,
We are trying to setup a pair of ZFS file servers, each backing-up data from
another.
The simplified setup is as follows:
server1
tank/prod/web
tank/backup/mail
server2
tank/prod/mail
tank/backup/web
server1:tank/prod/web is a test setup with 10GB of data for 60 websites.
server2:tank/p
