Hetz Ben Hamo
2017-Dec-29 15:16 UTC
[Gluster-users] cannot mount with glusterfs-fuse after NFS-Ganesha enabled
Hi, I've created a 2 node glusterFS test (Gluster 3.8). Without enabling NFS-Ganesha, when I try to mount from a client using glusterfs option - everything works. However, after enabling NFS-Ganesha, when I try to mount from a client using the glusterfs option (fuse), it fails with the following output (when using the log-file option): [2017-12-28 08:15:30.109110] I [MSGID: 100030] [glusterfsd.c:2412:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.8.4 (args: /usr/sbin/glusterfs --log-file=log --volfile-server=glnode1 --volfile-id=/gv0 /mnt) [2017-12-28 08:15:30.128685] I [MSGID: 101190] [event-epoll.c:628:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2017-12-28 08:15:30.132438] W [MSGID: 101095] [xlator.c:198:xlator_dynload] 0-xlator: /usr/lib64/glusterfs/3.8.4/xlator/features/ganesha.so: cannot open shared object file: No such file or directory [2017-12-28 08:15:30.132469] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume 'gv0-ganesha', line 68: type 'features/ganesha' is not valid or not found on this machine [2017-12-28 08:15:30.132489] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume gv0-ganesha [2017-12-28 08:15:30.132756] E [MSGID: 100026] [glusterfsd.c:2265:glusterfs_process_volfp] 0-: failed to construct the graph [2017-12-28 08:15:30.133054] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x3c1) [0x7f0d81334fb1] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x149) [0x7f0d8132f519] -->/lib64/libglusterfs.so.0(glusterfs_graph_destroy+0x84) [0x7f0d80e6edc4] ) 0-graph: invalid argument: graph [Invalid argument] [2017-12-28 08:15:30.133119] W [glusterfsd.c:1288:cleanup_and_exit] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x3c1) [0x7f0d81334fb1] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x172) [0x7f0d8132f542] -->/usr/sbin/glusterfs(cleanup_and_exit+0x6b) [0x7f0d8132eabb] ) 0-: received signum (1), shutting down [2017-12-28 08:15:30.133147] I [fuse-bridge.c:5817:fini] 0-fuse: Unmounting '/mnt'. [2017-12-28 08:15:30.136316] I [fuse-bridge.c:5822:fini] 0-fuse: Closing fuse connection to '/mnt'. Does this means that after enabling NFS-Ganesha, I cannot use the mount glusterfs-fuse on clients? I cannot upgrade to the latest gluster since in 3.12/3.13 all the nfs-ganesha stuff has been changed and there are no docs how to enable nfs-ganesha. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171229/4cf21b9f/attachment.html>
Hetz Ben Hamo
2017-Dec-29 15:33 UTC
[Gluster-users] cannot mount with glusterfs-fuse after NFS-Ganesha enabled
Answering to myself.. Gluster client was 3.8.4 while the gluster nodes were 3.8.15. After updating installing centos-release-gluster38.noarch on the client and performing update, everything works. On Fri, Dec 29, 2017 at 5:16 PM, Hetz Ben Hamo <hetz at hetz.biz> wrote:> Hi, > > I've created a 2 node glusterFS test (Gluster 3.8). > > Without enabling NFS-Ganesha, when I try to mount from a client using > glusterfs option - everything works. > > However, after enabling NFS-Ganesha, when I try to mount from a client > using the glusterfs option (fuse), it fails with the following output (when > using the log-file option): > > [2017-12-28 08:15:30.109110] I [MSGID: 100030] [glusterfsd.c:2412:main] > 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.8.4 > (args: /usr/sbin/glusterfs --log-file=log --volfile-server=glnode1 > --volfile-id=/gv0 /mnt) > [2017-12-28 08:15:30.128685] I [MSGID: 101190] [event-epoll.c:628:event_dispatch_epoll_worker] > 0-epoll: Started thread with index 1 > [2017-12-28 08:15:30.132438] W [MSGID: 101095] > [xlator.c:198:xlator_dynload] 0-xlator: /usr/lib64/glusterfs/3.8.4/xlator/features/ganesha.so: > cannot open shared object file: No such file or directory > [2017-12-28 08:15:30.132469] E [MSGID: 101002] [graph.y:212:volume_type] > 0-parser: Volume 'gv0-ganesha', line 68: type 'features/ganesha' is not > valid or not found on this machine > [2017-12-28 08:15:30.132489] E [MSGID: 101019] [graph.y:320:volume_end] > 0-parser: "type" not specified for volume gv0-ganesha > [2017-12-28 08:15:30.132756] E [MSGID: 100026] > [glusterfsd.c:2265:glusterfs_process_volfp] 0-: failed to construct the > graph > [2017-12-28 08:15:30.133054] E [graph.c:982:glusterfs_graph_destroy] > (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x3c1) [0x7f0d81334fb1] > -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x149) [0x7f0d8132f519] > -->/lib64/libglusterfs.so.0(glusterfs_graph_destroy+0x84) > [0x7f0d80e6edc4] ) 0-graph: invalid argument: graph [Invalid argument] > [2017-12-28 08:15:30.133119] W [glusterfsd.c:1288:cleanup_and_exit] > (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x3c1) [0x7f0d81334fb1] > -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x172) [0x7f0d8132f542] > -->/usr/sbin/glusterfs(cleanup_and_exit+0x6b) [0x7f0d8132eabb] ) 0-: > received signum (1), shutting down > [2017-12-28 08:15:30.133147] I [fuse-bridge.c:5817:fini] 0-fuse: > Unmounting '/mnt'. > [2017-12-28 08:15:30.136316] I [fuse-bridge.c:5822:fini] 0-fuse: Closing > fuse connection to '/mnt'. > > Does this means that after enabling NFS-Ganesha, I cannot use the mount > glusterfs-fuse on clients? > > I cannot upgrade to the latest gluster since in 3.12/3.13 all the > nfs-ganesha stuff has been changed and there are no docs how to enable > nfs-ganesha. > > Thanks >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171229/9a83ca7e/attachment.html>