[Gluster-users] single storage server

Whit Blauvelt whit.gluster at transpect.com
Fri May 6 16:05:03 UTC 2011

On Fri, May 06, 2011 at 04:46:19PM +0100, Nick Birkett wrote:

> What you are saying is that it is not a good idea to access the data directly even in the case
> of a single storage server when no glusterfs client is running on that server.

What I'm suggesting is that you mount the gluster storage locally like:

  mount -t glusterfs localhost:/gluster_share_name /local/mountpoint

Then you access the data directly at /local/mountpoint which, yes, involves
the fuse client. You're also going to have the data mounted at wherever you
had Gluster incorporate it from, so there's nothing stopping you from going
to it there and skipping fuse - except that if you make changes that way
there will be a lag at best before those file changes are recognized by any
remote systems you have which have mounted the Gluster share through their
own Gluster or NFS clients.

If you're not using any remote mounts, then what's Gluster doing for you? If
you are using them, taking the route to the data which skips fuse is going
to bollux things.

> I would like a difinitive answer on this from developers if possible.

I'll be surprised if I'm wrong. But it won't be a first ; >


More information about the Gluster-users mailing list