<div dir="ltr"><div><div><div><div><div>Hi,<br><br></div>From the information you provided, I am guessing that you have a replica 3 volume configured.<br></div>In that case you can run "gluster volume heal <volname>" which should do the trick for you.<br></div><br></div>Regards,<br></div>Karthik<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 8, 2018 at 6:16 AM, Frizz <span dir="ltr"><<a href="mailto:frizzthecat@googlemail.com" target="_blank">frizzthecat@googlemail.com</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><div><div>I have a setup with 3 nodes running GlusterFS.<br><br>gluster volume create myBrick replica 3 node01:/mnt/data/myBrick
node02:/mnt/data/myBrick node03:/mnt/data/myBrick
<br><br></div>Unfortunately node1 seemed to stop syncing with the other nodes, but this was undetected for weeks!<br><br></div>When I noticed it, I did a "service glusterd restart" on node1, hoping the three nodes would sync again.<br><br></div>But this did not happen. Only the CPU load went up on all three nodes + the access time went up.<br><div><div><br><div>When I look into the physical storage of the bricks, node1 is very different<br>
node01:/mnt/data/myBrick
: 9GB data<br>node02:/mnt/data/myBrick : 12GB data<br>node03:/mnt/data/myBrick
: 12GB data<br></div><div><br>How do I sync data from the healthy nodes Node2/Node3 back to Node1?<br></div></div></div></div>
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>