To reply to my own post:
After spending a huge amount of time this weekend trying to get 3.2.x NFS
stable in one way or another, I took the plunge and upgraded to 3.3.0.
After running some IO tests (iozone and dd), it has been good but the
verdict is still out depending on how it goes over the ne
Hi there,
We're using GlusterFS 3.2.7 currently and experiencing issue with NFS and
GlusterFS mounts. We were on 3.2.6 and had similar issues. Our install is
reasonably small. I'm tentative about moving to 3.3.x as we're looking for
a stable platform, not the latest features.
Our setup
-
On Sat, Jul 07, 2012 at 11:36:52PM -0300, Targino Silveira wrote:
>fusermount: failed to open /dev/fuse: Permission denied
>fusermount: failed to open /dev/fuse: Permission denied
>Mount failed. Please check the log file for more details.
Did you look in the log file?
ls -lrt /var/log
Hi,
I have a replica 2 setup that I use via Gluster NFS (3.3). Both bricks show
all files in sync (gluster volume heal info). I forced a sync the
new way (gluster volume heal all) and the old way (find /root/tmp/
-noleaf -print0 | xargs --null stat >/dev/null [gluster volume mounted at
/ro
I did try many options, I did try to on Ubuntu and Debian but no one a had
success, always I get this error mensage:
root@ct14274:~/downloads# glusterfs --version
glusterfs 3.2.7 built on Jun 11 2012 11:43:40
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster
