<html><head/><body><html><head></head><body>Please note the letter that precedes that message. That shows the level of the message. It tells you that the lock version numbers (which I read as serial numbers) don't match, so the fd is reestablished to bring them back into sync. It's informational and normal.<br>
<br>
You only, really, need to be concerned with "E" (error) and "C" (critical). <br><br><div class="gmail_quote">Toby Corkindale <toby.corkindale@strategicdata.com.au> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px">On 24/01/13 15:41, Toby Corkindale wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">I'm seeing these messages in logfiles a lot now, since upgrading to<br />3.3.1. What do they mean and how do I fix it? (I am running the same<br />version of Gluster on clients and servers, of course)<br /><br />"Server and Client lk-version numbers are not same, reopening the fds"<br />"Server lk version = 1"</blockquote><br />I should mention that I see this even on the storage servers themselves, <br />in glustershd.log. The client IP address there is reported as being its <br />own IP.<br /><br /><hr /><br />Gluster-users mailing list<br />Gluster-users@gluster.org<br /><a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br
/></pre></blockquote></div></body></html></body></html>