We have had some feedback/concerns raised regarding not including the messages
in the header file. Some external products do include the message strings in
the header files which helps for documentation as well as easier editing.
Does anyone have any thoughts on this? The advantages are listed a
Hello,
I am currently using gluster replication to share a common filesystem
across multiple nodes. Part of my application is a directory watcher that
will end up doing a stat on a glob of file patterns. What I am seeing is
that gluster will start using roughly 300kBps per watched pattern. Will
gl
Hi,
Completely forgot to say this is a mount on the same server.
On 6 May 2014 21:17, "Gavin Henry" wrote:
> Hi all,
>
> We use glusterfs with our SIP cluster for hosted SIP endpoints/phones.
> This is set up in replicated mode for lua scripts, voicemails (wav
> files), faxes (PDF's/tiffs) and c
Hi all,
We use glusterfs with our SIP cluster for hosted SIP endpoints/phones.
This is set up in replicated mode for lua scripts, voicemails (wav
files), faxes (PDF's/tiffs) and call recordings (wav/mp3). We're
trying to find more information on the time differences between a "du"
on a brick, i.e.
I will.
Cristiano Corsani, PhD
--
web: http://www.cryx.it
mail: ccors...@gmail.com
Il 06/mag/2014 19:08 "Kaushal M" ha scritto:
> Try disabling the open-behind translator. This should allow the 3.3
> clients to mount the volume.
> # gluster volume set performance.open-behind
Try disabling the open-behind translator. This should allow the 3.3 clients
to mount the volume.
# gluster volume set performance.open-behind off
~kaushal
On Tue, May 6, 2014 at 4:49 PM, Cristiano Corsani wrote:
> > Your 3.4 cluster is a newly deployed one or a upgraded one ( from 3.3)?
> > If
Hi Anand,
Thanks to come-up with the nice design. I have couple of comments.
1. It should be mention in the design the access-protocols that should be
used(NFS/CIFS etc) although the requirement states that.
2. Consideration section:
"Again, this is not a performance oriented feature. Rather,
I had seen the new "create push-pem" option and gave it a try today. I
> see that it does indeed create a different key with a different command
> in the authorized_keys file.
>
> One question remains though and this stems back to bug #
>
>
> 1091079.
> push-pem expects you to have setup pass
On Wed, 30 Apr 2014 20:25:03 +0100
James Le Cuirot wrote:
> > > On April 28, 2014 6:03:16 AM PDT, Venky Shankar
> > > wrote:
>
> > >> On 04/27/2014 11:55 PM, James Le Cuirot wrote:
> > >>> I'm new to Gluster but have successfully tried geo-rep with
> > >>> 3.5.0. I've read about the new tar+ssh
> Your 3.4 cluster is a newly deployed one or a upgraded one ( from 3.3)?
> If yours are newly deployed, you could not use 3.3 client to mount for the
> op version is set 2
Is a new one.
> If yours are upgraded one, you could use 3.3 client to mount for the op
> version is set 1.
> the op version
Your 3.4 cluster is a newly deployed one or a upgraded one ( from 3.3)?
If yours are newly deployed, you could not use 3.3 client to mount for the
op version is set 2
If yours are upgraded one, you could use 3.3 client to mount for the op
version is set 1.
the op version is newly introduced in 3.4
Hi all. I have many clients 3.3.1 (I can't upgrade because of an old
distro version) I would like to mount a 3.4 or 3.5 volume.
>From documentation it seems that 3.3.x is compatible with 3.4. But it
does not work. The error is "unable to get the volume file from
server".
My systems (server and cli
12 matches
Mail list logo
