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 nor
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.
You only, really, need to be c
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 t
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"
Side note: The same annoying conversions seems to happen when using Skype.
On Wed, Jan 23, 2013 at 5:29 PM, Toby Corkindale <
toby.corkind...@strategicdata.com.au> wrote:
> On 24/01/13 10:57, Joe Julian wrote:
>
>> On 01/23/2013 03:43 PM, Toby Corkindale wrote:
>>
>>> Hi,
>>> Last night I attemp
On 24/01/13 10:57, Joe Julian wrote:
On 01/23/2013 03:43 PM, Toby Corkindale wrote:
Hi,
Last night I attempted to upgrade some GlusterFS servers from 3.2.x to
3.3.1.
The upgrade did NOT go smoothly, and I'm quite disappointed in the
documentation for the upgrade as it was quite erroneous.
I fo
On 01/23/2013 03:43 PM, Toby Corkindale wrote:
Hi,
Last night I attempted to upgrade some GlusterFS servers from 3.2.x to
3.3.1.
The upgrade did NOT go smoothly, and I'm quite disappointed in the
documentation for the upgrade as it was quite erroneous.
I followed this guide:
http://www.glus
Hi,
Last night I attempted to upgrade some GlusterFS servers from 3.2.x to
3.3.1.
The upgrade did NOT go smoothly, and I'm quite disappointed in the
documentation for the upgrade as it was quite erroneous.
I followed this guide:
http://www.gluster.org/2012/05/upgrading-to-glusterfs-3-3-0/
T
First - thanks for taking the time and providing the reply.
Due to a bad flu I was unable to verify till now but now saw we use fstream
in our apps, to write the files. Assumed the buffer was large, but never
tested it.
We have increased the fstream buffer to 100MB and will check if this helps
(t
