Hi RedHat GlusterFS users,
Last week-end, I worked on a GlusterFS cluster upgrade, from 3.0.3 to 3.3.0.
We were using hand-made volume files defining 2 volumes, a distributed one,
and a replicated-distribute one; both using the transport-type ib-verbs
option.
One of our objectives was to use
Say, is it possible to compile a kernel without whatever part of its NFS
support competes with Gluster's locking?
Whit
On Fri, Jul 13, 2012 at 08:14:27AM -0400, Rajesh Amaravathi wrote:
I hope you do realize that two NLM implementations of the same version
cannot operate simultaneously in the
Dear All,
I am having a lot of trouble accessing GlusterFS 3.2.6 volumes from
Solaris 10 NFS clients. Volumes can be mounted but I/O performance is
so poor that the volumes are practically unusable. Doing cd or ls can
take a very long time and often hangs, with repeated errors like the
There were a lot of changes in NFS filehandle management in 3.3.0. Can you
check if these performance issue has been addressed with those changes?
Avati
On Mon, Jul 16, 2012 at 11:42 AM, Dan Bretherton
d.a.brether...@reading.ac.uk wrote:
Dear All,
I am having a lot of trouble accessing
Hello Avati,
Thanks for your quick response. I had planned to upgrade to 3.3 at some
point, mainly to take advantage of the NFS memory leak fix.
I am worried about upgrading after bad experiences with 3.1.0 and
3.2.0. Does anyone have any experience of upgrading from 3.2.6 to 3.3.0?
-Dan.
On 07/16/2012 12:16 PM, Philippe Muller wrote:
Here is what I found: - On page 123 of the GlusterFS Administration
Guide 3.3.0, a small note saying: NOTE: with 3.3.0 release,
transport type 'rdma' and 'tcp,rdma' are not fully supported.
I don't see this indicated in the 3.2.x series, though
On Mon, Jul 16, 2012 at 12:37 PM, Joe Landman
land...@scalableinformatics.com wrote:
On 07/16/2012 12:16 PM, Philippe Muller wrote:
Here is what I found: - On page 123 of the GlusterFS Administration
Guide 3.3.0, a small note saying: NOTE: with 3.3.0 release,
transport type 'rdma' and
On 07/16/2012 03:39 PM, Anand Avati wrote:
It only means we had to push out RDMA support to 3.3.1 (or 3.3.2) for
internal resource scheduling reasons.
Ok, thanks.
Avati
--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics Inc.
email: land...@scalableinformatics.com
web :
