<div dir="ltr"><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Perhaps you can use this tools:<br><a href="https://aravindavk.in/blog/gluster-georep-tools/">https://aravindavk.in/blog/gluster-georep-tools/</a><br></div><div><br></div><div>I am using it with great success.</div><div><div><p style="font-size:12.8px;margin:0px"></p><p style="font-size:12.8px;margin:0px"><br></p><p style="font-size:12.8px;margin:0px"><br></p></div></div><div><br></div></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em qui., 22 de ago. de 2024 às 17:36, Karl Kleinpaste <<a href="mailto:karl@kleinpaste.org">karl@kleinpaste.org</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>

  
    
  
  <div>
    <div>On 8/22/24 14:08, Strahil Nikolov
      wrote:<br>
    </div>
    <blockquote type="cite">I can
      try to reproduce it if you could provide the gluster version,
      operating system and volume options.</blockquote>
    <br>
    <font face="FreeSerif">Most kind.<br>
      <br>
      Fedora39,  Packages:<br>
      <br>
    </font><font face="monospace">$ grep gluster /var/log/rpmpkgs<br>
      gluster-block-0.5-11.fc39.x86_64.rpm<br>
      glusterfs-11.1-1.fc39.x86_64.rpm<br>
      glusterfs-cli-11.1-1.fc39.x86_64.rpm<br>
      glusterfs-client-xlators-11.1-1.fc39.x86_64.rpm<br>
      glusterfs-cloudsync-plugins-11.1-1.fc39.x86_64.rpm<br>
      glusterfs-coreutils-0.3.2-1.fc39.x86_64.rpm<br>
      glusterfs-events-11.1-1.fc39.x86_64.rpm<br>
      glusterfs-extra-xlators-11.1-1.fc39.x86_64.rpm<br>
      glusterfs-fuse-11.1-1.fc39.x86_64.rpm<br>
      glusterfs-geo-replication-11.1-1.fc39.x86_64.rpm<br>
      glusterfs-resource-agents-11.1-1.fc39.noarch.rpm<br>
      glusterfs-server-11.1-1.fc39.x86_64.rpm<br>
      glusterfs-thin-arbiter-11.1-1.fc39.x86_64.rpm<br>
      libglusterfs0-11.1-1.fc39.x86_64.rpm<br>
      libvirt-daemon-driver-storage-gluster-9.7.0-4.fc39.x86_64.rpm<br>
      python3-gluster-11.1-1.fc39.x86_64.rpm<br>
      qemu-block-gluster-8.1.3-5.fc39.x86_64.rpm</font><font face="FreeSerif"><br>
      <br>
      (Somewhere along the way, I'm sure I just did "dnf install
      *gluster*".)<br>
      <br>
      The two volumes were created using the quick start guide:<br>
      <a href="https://docs.gluster.org/en/main/Quick-Start-Guide/Quickstart/" target="_blank">https://docs.gluster.org/en/main/Quick-Start-Guide/Quickstart/</a><br>
      which means that, after establishing peering, I used these simple
      commands:<br>
      <br>
      (on pjs) gluster volume create j pjs:/xx/brick<br>
      (on pms) gluster volume create n pms:/xx/brick<br>
      <br>
      where /xx on these 2 systems are small, spare, otherwise empty,
      identical filesystems of about 40G, formatted ext4. No other
      options were used in creation.<br>
      <br>
      As I said in my initial note, it seems that the underlying problem
      (from logged complaints) is lack of a</font><font face="FreeSerif">
      geo-rep</font><font face="FreeSerif"> template configuration from
      which to set up, and I simply don't know where/how/when that
      should have been created. But this is just a surmise on my part.<br>
    </font>
  </div>

________<br>
<br>
<br>
<br>
Community Meeting Calendar:<br>
<br>
Schedule -<br>
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br>
Bridge: <a href="https://meet.google.com/cpu-eiue-hvk" rel="noreferrer" target="_blank">https://meet.google.com/cpu-eiue-hvk</a><br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div>