Question

Glusterfs is not working as client

  • Posted September 2, 2014

Hello,

I’m currently following this tutorial: https://www.digitalocean.com/community/articles/how-to-create-a-redundant-storage-pool-using-glusterfs-on-ubuntu-servers

Even thow I use debian wheezy insted of ubuntu (of course, I didn’t use the same repository as the tutorial).

I managed to configure the server, but when I’m trying to configure the client, it isn’t working. When I exec this command: mount -t glusterfs <Ip server>:Test01 /mnt/Test01/ I get this error: Mount failed. Please check the log file for more details.

And in the logs files, I get

[2014-09-02 12:23:59.365747] I [glusterfsd.c:1959:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.5.2 (/usr/sbin/glusterfs --volfile-server=<My server Ip, I changed the log> --volfile-id=Test01 /mnt/Test01/)
[2014-09-02 12:23:59.371218] E [mount.c:267:gf_fuse_mount] 0-glusterfs-fuse: cannot open /dev/fuse (No such device)
[2014-09-02 12:23:59.371332] E [xlator.c:403:xlator_init] 0-fuse: Initialization of volume 'fuse' failed, review your volfile again

A lots of website saying their had difficulty with fuse because of the boot order, but since I doing this command manually, it should not be affected by this.

One thing I saw is that on debian wheezy there is no file with the name fuse in /etc/init.d, even thow fuse is installed on the server.

Thank you

Subscribe
Share

Were you able to address this? Perhaps try creating the mount with:

mknod -m 666 /dev/fuse c 10 229


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

This question was answered by @BrookDO:

Were you able to address this? Perhaps try creating the mount with:

mknod -m 666 /dev/fuse c 10 229

View the original comment