I also using csync2 to sync git repos, and had similar problem,
at the end I came out with this setup,
I had to exclude the index file from csync2 and sync it using rsync
had to use new host alias called you in /etc/hosts to point to the next
host (in 2 node setup).
hope this help.

        include /tftpboot;
>
>         exclude *~ index;
>
>         action
>         {
>                 pattern /tftpboot/xxx/.git/*;
>                 exec "rsync -vic you:/tftpboot/xxx/.git/index
> /tftpboot/xxx/.git/index";
>                 logfile "/var/log/csync2_action.log";
>         }
>
>         action
>         {
>                 pattern /tftpboot/yyy/.git/*;
>                 exec "rsync -vic you:/tftpboot/yyy/.git/index
> /tftpboot/yyy/.git/index";
>                 logfile "/var/log/csync2_action.log";
>         }
>






───



On 21 December 2017 at 03:43, Dominik George <n...@naturalnet.de> wrote:

> Hi,
>
> we are having strange issues with syncing directories containing clones
> of git repositories. We were using unison before, and it suspiciously
> showed the same issues…
>
> What happends is hard to describe, but it looks like the git index gets
> broken. The effect is that all nodes in the cluster end up with a broken
> state, namely with a lot of untracked files in the repository.
>
> Some details that might be of interest:
>
>  * In the synced directory tree, there are several clones of the same
>    git repository
>  * Changes are made only on one node
>  * csync is configured to prefer the younger copy of a file
>
> Any ideas on that?
>
> Cheers,
> Nik
>
> _______________________________________________
> Csync2 mailing list
> Csync2@lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/csync2
>
>
_______________________________________________
Csync2 mailing list
Csync2@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/csync2

Reply via email to