<div dir="ltr">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?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 23, 2015 at 9:58 AM, Gabriel Kuri <span dir="ltr"><<a href="mailto:gkuri@ieee.org" target="_blank">gkuri@ieee.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>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? <br><br></div>Thanks ...<br></div>
</blockquote></div><br></div>