<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 1, 2015 at 11:51 AM, Krishnan Parthasarathi <span dir="ltr"><<a href="mailto:kparthas@redhat.com" target="_blank">kparthas@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> We do have a way to tackle this situation from the code. Raghavendra<br>
> Talur will be sending a patch shortly.<br>
<br>
</span>We should fix it by undoing what daemon-refactoring did, that broke the lazy creation<br>
of uuid for a node. Fixing it elsewhere is just masking the real cause.<br>
Meanwhile 'rm' is the stop gap arrangement.<br></blockquote><div><br></div><div>Agreed. </div><div>The patch I was supposed to send may not solve this issue</div><div>.</div><div>Atin understands this code well better than I and I guess would be sending the patch</div><div>to generate uuid on first volume creation or first peer probe instead of on</div><div>first start of glusterd.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><font color="#666666"><b>Raghavendra Talur </b></font><div><br></div></div></div>
</div></div>