I was under the impression that self-mounting NFS of any kind (mount -t
nfs localhost...) was a dangerous thing. When I did that with gNFS I
could cause a server to crash in no time at all with a simple dd into
the mount point. I was under the impression that kNFS would have the
same problem
On 09/17/2012 06:08 AM, Jeff White wrote:
I was under the impression that self-mounting NFS of any kind (mount
-t nfs localhost...) was a dangerous thing. When I did that with gNFS
I could cause a server to crash in no time at all with a simple dd
into the mount point. I was under the
Just to clarify, we are using the native kNFS-server from the distro, not
gluster's NFS implementation. Note that CentOS 5.7/5.8 does not seem to
support this kind of loopback mounting with the kNFS version they use (kNFS
ver 1.0.8/9).
However, the recent kNFS servers from Ubuntu/Debian
Hi Harry,
There is a compression translator in Gerrit which you might be
interested in: http://review.gluster.org/#change,3251
It compresses data (using zlib library) before it is sent out to the
network from the server and on the other side (client; FUSE mount) it
decompresses it. Also,
Hi Venky - thank for the link to this translator. I'll take a look at it, but
right now, we don't have too much trouble with reads - it's the 'zillions of
tiny writes' problem that's hosing us and the NFS solution gives us a bit more
headroom.
We'll be moving this out to part of our cluster
- Original Message -
Hi Venky - thank for the link to this translator. I'll take a look
at it, but
right now, we don't have too much trouble with reads - it's the
'zillions of
tiny writes' problem that's hosing us and the NFS solution gives us a
bit more
headroom.
We'll be
On Fri, Sep 14, 2012 at 09:41:42AM -0700, harry mangalam wrote:
What I mean:
- mounting a gluster fs via the native client,
- then NFS-exporting the gluster fs to the client itself
- then mounting that gluster fs via NFS3 to take advantage of the
client-side caching.
Harry,
What
Well, it was too clever for me too :) - someone else suggested it when I was
describing some of the options we were facing. I admit to initially thinking
that it was silly to expect better performance by stacking protocols, but we
tried it and it seems to have worked.
To your point:
the
A note on recent history:
There were past attempts to export GlusterFS client mounts over NFS, but those
used the GlusterFS NFS service. I believe this is the first instance in the
wild of someone trying this with knfsd.
With the former, while there was increased performance, there would
Hi All,
We have been experimenting with 'protocol stacking' - that is, running gluster
over NFS.
What I mean:
- mounting a gluster fs via the native client,
- then NFS-exporting the gluster fs to the client itself
- then mounting that gluster fs via NFS3 to take advantage of the client-side
10 matches
Mail list logo
