<div dir="ltr"><div><div><div><div>Atin,<br><br></div>Couple of quick questions about the upgrade and in general about the meaning of some of the parameters in the glusterd dir..<br><br></div><div>- I dont see the quota-version in the volume info file post upgrade, so did the upgrade not go through properly? <br></div>- What does the op-version in the volume info file mean? Does this have any corelation with the cluster op-version? Does it change with an upgrade?<br></div>- A more basic question - should all peer probes always be done from the same node or can they be done from any node that is already in the cluster? The reason I ask is when I tried to do what was said in <a href="http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/">http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/</a> the initial cluster was initiated from node A with 5 other peers. Then post upgrade, node B which was in the cluster got a peer rejected. So I deleted all the files except <a href="http://glusterd.info">glusterd.info</a> and then did a peer probe of A from B. Then when I ran a peer status on A, it only showed one node, B. Should I have probed B from A instead?<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jul 23, 2016 at 10:48 AM, Atin Mukherjee <span dir="ltr"><<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am suspecting it to be new quota-version introduced in the volume info file which may have resulted in a checksum mismatch resulting into peer rejection. But we can confirm it from log files and respective info file content.<div class="HOEnZb"><div class="h5"><span></span><br><br>On Saturday 23 July 2016, B.K.Raghuram <<a href="mailto:bkrram@gmail.com" target="_blank">bkrram@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Unfortunately, the setup is at a customer's place which is not remotely accessible. Will try and get it by early next week. But could it just be a mismatch of the /var/lib/glusterd files? <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 22, 2016 at 8:07 PM, Atin Mukherjee <span dir="ltr"><<a>amukherj@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Glusterd logs from all the nodes please?<div><div><span></span><br><br>On Friday 22 July 2016, B.K.Raghuram <<a>bkrram@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>When we upgrade some nodes from 3.6.1 to 3.7.13, some of the nodes give a peer status of "peer rejected" while some dont. Is there a reason for this discrepency and will the steps mentioned in <a href="http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/" target="_blank">http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/</a> work for this as well?<br><br></div>Just out of curiosity, why the line "Try the whole procedure a couple more times if it doesn't work right
away." in the link above?<br></div>
</blockquote><br><br></div></div><span><font color="#888888">-- <br>Atin<br>Sent from iPhone<br>
</font></span></blockquote></div><br></div>
</blockquote><br><br>-- <br>Atin<br>Sent from iPhone<br>
</div></div></blockquote></div><br></div>