Must be something wrong with your mount.glusterfs script, you could try
running it with sh -x to see what command it tries to run.
On Tue, 2015-01-27 at 07:28 +0100, Bart?omiej Syryjczyk
wrote:> W dniu 2015-01-27 o 02:54, Pranith Kumar Karampuri pisze:
> >
> > On 01/26/2015 02:27 PM, Bart?omiej Syryjczyk wrote:
> >> W dniu 2015-01-22 o 17:37, A Ghoshal pisze:
> >>> Maybe start the mount daemon from shell, like this?
> >>>
> >>> /usr/sbin/glusterfs --debug --volfile-server=glnode1
> >>> --volfile-id=/testvol /mnt/gluster
> >>>
> >>> You could get some useful debug data on your terminal.
> >>>
> >>> However, it's more likely you have a configuration related
problem
> >>> here. So the output of the following might also help:
> >>>
> >>> ls -la /var/lib/glusterd/vols/glnode1/
> >>>
> >> When I start mount daemon from shell it's works fine.
> >> After mount with -o log-level=DEBUG, I can see this:
> >> ---
> >> [...]
> >> [2015-01-26 08:19:48.191675] D
[fuse-bridge.c:4817:fuse_thread_proc]
> >> 0-glusterfs-fuse: *terminating upon getting ENODEV when reading
> >> /dev/fuse*
> > Could you check if the device is present or not, using the following
> > command?
> > 07:16:10 :) ? ls /dev/fuse -l
> > crw-rw-rw-. 1 root root 10, 229 Jan 25 07:31 /dev/fuse
> I sent it earlier (difference is that I've got SELinux disabled)
>
> >>
> >> [root at apache2 ~]# ls -l /dev/fuse
> >> crw-rw-rw- 1 root root 10, 229 Jan 26 09:19 /dev/fuse
>