On Mon, Feb 04, 2013 at 12:21:29PM +0100, Stian Brattland wrote: > I'm running with a setup where Csync2 gets triggered by Lsyncd upon file > changes. This works very well, > and files replicate fine to other machines.
The thing is: it seems to work well, but it actually isn't. Lsyncd is good software, doing what I did with csync2id.pl (see contrib). But if you are lagging, your inotify queue will be overun. I fixed it by queueing inotify items as hints with the -h option. In a seperate thread I was doing csync2 -c (that without arguments empties the hint queue), and after that csync2 -u the dirty list. It worked pretty good in 10M files with 10 changes per second, on pretty old hardware. (I now use mogilefs for that). In other cases (not related to inotify queue overflow) it usually is related to nodes not initialized correctly: nodes will have a different view on what other nodes already have. Try csync2 -T <thisnode> <othernode> -UI to create an update list based on database contents only. _______________________________________________ Csync2 mailing list Csync2@lists.linbit.com http://lists.linbit.com/mailman/listinfo/csync2
