Gluster users - Jun 2015 - geo-replication initial sync of volume

Running Gluster 3.6.3, I'm seeing odd (possibly buggy) behavior with the
initial sync of the master -> slave on a new geo-rep volume. If I create
the geo-rep volume and start it, all of the existing files in the master
volume won't get synced over to the slave. Any new files that are created
after the geo-rep is created are synced to the slave. Do I need to do
anything to tell the master to sync existing files from the master -> slave
after creating the geo-rep?

Thanks ...
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150623/023972e6/attachment.html>

I tried out Gluster 3.7.2 and it appears to work fine, after the geo-rep is
created, all of the existing files on the master volume appear to get
copied over to the slave. Is there a known bug in 3.6.3 that would prevent
this?

On Tue, Jun 23, 2015 at 9:58 AM, Gabriel Kuri <gkuri at ieee.org> wrote:
> Running Gluster 3.6.3, I'm seeing odd (possibly buggy) behavior with
the
> initial sync of the master -> slave on a new geo-rep volume. If I create
> the geo-rep volume and start it, all of the existing files in the master
> volume won't get synced over to the slave. Any new files that are
created
> after the geo-rep is created are synced to the slave. Do I need to do
> anything to tell the master to sync existing files from the master ->
slave
> after creating the geo-rep?
>
> Thanks ...
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150623/3099c872/attachment.html>