What I did as a "quick solution" is a little python script that using "inotify" intercepts every file modified/created/deleted on a few selected paths. Those files are inserted in a queue, that's "rsynced" by another process to the rest of servers :D

The current version of ChironFS (1.0RC9) waits until all thewrites are done to return to the caller. So it is a problemif you have a slow link. I am currently working on version 1.1 to implement asynchronous I/O (and, in the near future, Hot Resync). This way ChironFS will return just after the first successful write. The others writes will be handled by callbacks and the control of what replica is working or notwill still work as it does now. So, write operations are expected to have a very high speed increment.

Also, I would be very grateful if you could provide somefeedback about the usage and stability of ChironFS. Aslong as I have tested it is working without any bug. Butit would be good if I have other people's report. The lackof feedback is the main reason I didn't change the statusof beta-RC to stable.