[Gluster-users] gluster 3.4 or 3.5 compatibility with 3.3.x

Kaushal M kshlmster at gmail.com
Tue May 6 17:08:20 UTC 2014


Try disabling the open-behind translator. This should allow the 3.3 clients
to mount the volume.
# gluster volume set <volname> performance.open-behind off

~kaushal


On Tue, May 6, 2014 at 4:49 PM, Cristiano Corsani <ccorsani at gmail.com>wrote:

> > 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 is newly introduced in 3.4
>
> Is there a way to manage it or let it works in 3.5?
>
> My problem is that I have over 100 clients whose home directory are stored
> in
> an old storage. I would like to migrate to glusterfs but clients are
> old distro and
> plugging the glusterfs is the first step to upgrade the client too.
> Otherwise I will
> use NFS.
>
> --
> Cristiano Corsani, PhD
> -------------------------------------
> http://www.cryx.it
> info at cryx.it
> ccorsani at gmail.com
> ------------------------------
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140506/1e88a454/attachment.html>


More information about the Gluster-users mailing list