There were some posts regarding incompatibility between versions due to the insecure ports option. http://www.gluster.org/pipermail/gluster-users/2015-August/023207.html. Perhaps worth a shot ?
On Wed, Sep 23, 2015 at 3:20 PM, Gluster Admin <[email protected]> wrote: > I would love to know if i am doing something wrong but as it stands I have > a redhat gluster 3.1 setup and the only native FUSE clients i can get to > work are redhat. I have had no success with Centos 6/7 and various gluster > clients or OEL 6 in same case. > > I am hoping there is some option or something I am not setting and this > will actually work. > > On Wed, Sep 23, 2015 at 3:11 PM, Prasun Gera <[email protected]> > wrote: > >> Is this confirmed ? I have held off upgrading from 3.0 to 3.1. I have a >> lot of Ubuntu clients who are using the ppa for the fuse clients. I don't >> want to upgrade if it's known to break things. >> >> On Wed, Sep 23, 2015 at 10:40 AM, Gluster Admin <[email protected]> >> wrote: >> >>> Just curious here if RH is purposely trying to prevent anyone but RHEL >>> servers using their storage natively via the FUSE client? >>> >>> with RHGS 3.1 I can mount via fuse with no issues on RHEL 6/7 clients >>> but no other variant of Gluster 3.6 or 3.7 client can connect to it. Even >>> tried installing the RHGS fuse and client libs with no success. Same if i >>> try to mount Gluster 3.7 from RHEL with FUSE so its both ways. >>> >>> Just a bummer as we have tons of non RHEL clients and would prefer not >>> to setup NFS HA when the native client performs pretty well and covers all >>> the HA without the hassle. >>> >>> >>> >>> _______________________________________________ >>> Gluster-users mailing list >>> [email protected] >>> http://www.gluster.org/mailman/listinfo/gluster-users >>> >> >> >
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
