Re: [Gluster-users] Performance gluster 3.2.5 + QLogic Infiniband

2012-05-05 Thread Bryan Whitehead
> I am copying the "gluster volume info all" output below. > > Sorry about the confusion with IPoIB and RDMA. > > I am using RDMA on the main-volume (mount -t glusterfs > cfdstorage01-ib:main-volume.rdma /cfd/data) and IPoIB on backup volume > (mount -t glusterfs cfdstorage01-ib:backup-volume /cfd/

Re: [Gluster-users] Gluster client can't connect to Gluster volume

2012-05-05 Thread Eric
Thanks, David: That's fine. If it's just a version-mismatch I can accept that. I'm sure that the developers at Mageia are working on catching-up in Mageia, Version 2. I just figured that, if it were a version-mismatch, I'd see something to that effect in the servers' log files. That's all. Er

Re: [Gluster-users] Gluster client can't connect to Gluster volume

2012-05-05 Thread David Coulson
There's probably not a whole lot of 'fixing' since the two versions are so different. You can tell the package maintainer to make a 3.2.6 build. That'll help. On 5/5/12 1:43 PM, Eric wrote: Thanks, David: But I'd rather see if I can fix the problem with the Mageia client (|glusterfs-client-3

Re: [Gluster-users] Gluster client can't connect to Gluster volume

2012-05-05 Thread Eric
Thanks, David: But I'd rather see if I can fix the problem with the Mageia client (glusterfs-client-3.0.0-2.mga1): * This will allow me to file a bug report with the package maintainer (if necessary). * I already know that the systems that have Gluster 3.2.6 from source [i.e., t

Re: [Gluster-users] Gluster client can't connect to Gluster volume

2012-05-05 Thread David Coulson
That's way old documentation. Start by installing 3.2.6 on your client and see if it works then. I don't think anyone expects 3.2 and 3.0 to work correctly. On 5/5/12 12:09 PM, Eric wrote: Thanks, David: Yes... * iptables has been disabled on all three systems. * SELinux is set to permi

Re: [Gluster-users] Gluster client can't connect to Gluster volume

2012-05-05 Thread Eric
Thanks, Xavier: SELinux is set to permissive on the two systems that have it. Eric Pretorious Truckee, CA > > From: Xavier Normand >To: Eric >Cc: "gluster-users@gluster.org" >Sent: Friday, May 4, 2012 9:57 PM >Subject: Re: [Gluster-users] Gluster client can

Re: [Gluster-users] Gluster client can't connect to Gluster volume

2012-05-05 Thread Eric
Thanks, David: Yes... * iptables has been disabled on all three systems. * SELinux is set to permissive on the two systems that employ it - the two CentOS nodes. * Port #6996 is referenced in the Troubleshooting section of the Gluster User Guide. FWIW: All of this except

Re: [Gluster-users] Gluster client can't connect to Gluster volume

2012-05-05 Thread David Coulson
Do you have any firewall rules enabled? I'd start by disabling iptables (or at least setting everything to ACCEPT) and as someone else suggested setting selinux to permissive/disabled. Why are your nodes and client using different versions of Gluster? Why not just use the 3.2.6 version for eve