Hide Forgot
When mounting a GlusterFS volume in fstab at boot, this always fails due to fuse not being loaded at the time fstab wants to mount the GlusterFS volume. fstab line: /etc/glusterfs/glusterfs.vol /dfs1 glusterfs defaults,log-file=/var/log/glusterfs.log 0 0 /var/log/glusterfs.log shows: [2010-11-23 07:11:12] E [mount.c:525:fuse_mount_sys] glusterfs-fuse: cannot open /dev/fuse (No such file or directory) [2010-11-23 07:11:12] N [mount.c:602:gf_fuse_mount] glusterfs-fuse: direct mount failed (No such file or directory), retry to mount via fusermount [2010-11-23 07:11:12] E [mount.c:626:gf_fuse_mount] glusterfs-fuse: mount failed [2010-11-23 07:11:12] E [xlator.c:844:xlator_init_rec] fuse: Initialization of volume 'fuse' failed, review your volfile again [2010-11-23 07:11:12] E [glusterfsd.c:591:_xlator_graph_init] glusterfs: initializing translator failed [2010-11-23 07:11:12] E [glusterfsd.c:1395:main] glusterfs: translator initialization failed. exiting
GlusterFS does not modprobe fuse before mounting. Can you please modprobe fuse and then start GlusterFS?
Modprobing FUSE doesn't work, modprobe says it can't find the module fuse. I am running GlusterFS inside a VPS and it seems that FUSE was compiled without a 'modprobable' module or something...I don't know that much about modules etc. so really can't figure out how this works. Modprobe says it can't find fuse, but mounting the GlusterFS volume manually does work. (mount also show the fusectrl mount, so FUSE does work)
On lack of feedback I close this bug. If OP would happen to look back, we can reopen.