[Gluster-users] "Server and Client lk-version numbers are not same"

Toby Corkindale toby.corkindale at strategicdata.com.au
Thu Jan 24 05:37:33 UTC 2013


On 24/01/13 16:30, Joe Julian wrote:
> 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.

OK, thanks.
It seems concerning as it happens quite frequently now; you'd assume 
that they should have stayed in sync once "the fd was reopened".

>
> You only, really, need to be concerned with "E" (error) and "C" (critical).
>
> Toby Corkindale <toby.corkindale at strategicdata.com.au> wrote:
>
>     On 24/01/13 15:41, Toby Corkindale wrote:
>
>         I'm seeing these messages in logfiles a lot now, since upgrading to
>         3.3.1. What do they mean and how do I fix it? (I am running the same
>         version of Gluster on clients and servers, of course)
>
>         "Server and Client lk-version numbers are not same, reopening
>         the fds"
>         "Server lk version = 1"
>
>
>     I should mention that I see this even on the storage servers themselves,
>     in glustershd.log. The client IP address there is reported as being its
>     own IP.
>





More information about the Gluster-users mailing list