> Try disabling the open-behind translator. This should allow the 3.3 clients
> to mount the volume.
> # gluster volume set performance.open-behind off
It works but I can see only the main directory of the volume. No
access to files in
them. I've checked user rights, they're ok. So at the end it
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
> 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
