I'm after one that would suit multiple clients (laptops typically) in a "business/home" usage scenario with very intermittent connectivity.
Right now, I have a central fileserver at home which is backed up properly and similar at work. I work mostly on a laptop (which is the way everyone in my family and most of my work colleagues are going. I occasionally sync back to my home server and work servers with unison over ssh, which is a great tool.
I'm not looking for a caching solution that depends on the network being there — I'm after a full on replicated (at the file level, not the block) filesystem preferably with no concept of a master (unison handles this quite well).
So there seem to be a couple of directions I could take:
1) Run unison as root from a script with a carefully chosen config file per FS area. Write a script runs when (say) at-home WiFi is detected, so as to avoid syncing over a mobile link. Email errors to me for manual fixing (unison generally "does the right thing" and baulks before doing something that is not provably correct).
2) Find a more elegant solution that works at the kernel or daemon level.
1 — Anyone done this and did it work out?
2 — Are there any well maintained linux network filesystems worth looking at that would behave well in a WAN-with-intermittent-connectivity context?