<div dir="ltr"><a class="gmail_plusreply" id="plusReplyChip-0" href="mailto:srakonde@redhat.com" tabindex="-1">+Sanju Rakonde</a> & <a class="gmail_plusreply" id="plusReplyChip-1" href="mailto:amukherj@redhat.com" tabindex="-1">+Atin Mukherjee</a> adding glusterd folks who can help here.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 27, 2019 at 3:24 PM Riccardo Murri <<a href="mailto:riccardo.murri@gmail.com">riccardo.murri@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I managed to put the reinstalled server back into connected state with<br>
this procedure:<br>
<br>
1. Run `for other_server in ...; do gluster peer probe $other_server;<br>
done` on the reinstalled server<br>
2. Now all the peers on the reinstalled server show up as "Accepted<br>
Peer Request", which I fixed with the procedure outlined in the last<br>
paragraph of <a href="https://docs.gluster.org/en/v3/Troubleshooting/troubleshooting-glusterd/#debugging-glusterd" rel="noreferrer" target="_blank">https://docs.gluster.org/en/v3/Troubleshooting/troubleshooting-glusterd/#debugging-glusterd</a><br>
<br>
Can anyone confirm that this is a good way to proceed and I won't be<br>
heading quickly towards corrupting volume data?<br>
<br>
Thanks,<br>
Riccardo<br>
_______________________________________________<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>