jwiegley

No, nothing happened as far as I know. I stopped trying out BTSync, because even after I restricted it to non-ZFS volumes only, it just crashed/hung too much for me to trust any data to it. I'll wait a few revs for maturation I guess.

I have several ZFS filesystems attached to my Mac Pro, using the ZEVO Community Edition. I thought it would be perfect to use sync these filesystems with BTSync, as I would get versioning and compression of the data store for free, along with efficient syncing across my LAN. However, when run in this configuration, BTSync just keeps hanging. It starts scanning the volume, but then it pauses, gives me a spinning beachball of death, and then only becomes responsive again if I wait about a whole minute. But then it's only responsive for 1 or 2 seconds before the beachball comes back, and I have to wait a minute again. Rinse, wash, repeat. This effectively meant I couldn't use BTSync with Mac ZFS. Is there perhaps a bad interaction going on with the way that the filesystem is being monitored for changes? Thanks, John