Description of problem: ========================== Using fuse mount not able to mount sub-direcotries of the volume Version-Release number of selected component (if applicable): =========================== glusterfs-fuse-3.7.0-2.el6rhs.x86_64 How reproducible: Steps to Reproduce: ================= 1.Create a volume and mount entire volume on the client after that create few directories 2.Try to mount the sub-direcotries of the volume on differnt volume but mount operation failing with [root@localhost /]# mount -t glusterfs 10.70.33.229:/vol1/dir1/test /mnt/vol1/ Mount failed. Please check the log file for more details. Snippet of the log: ==================49185, attached to remote volume '/rajesh2/brick4'. [2015-05-19 10:43:45.202802] I [client-handshake.c:1474:client_setvolume_cbk] 0-vol1-client-0: Server and Client lk-version numbers are not same, reopening the fds [2015-05-19 10:43:45.203065] I [client-handshake.c:1462:client_setvolume_cbk] 0-vol1-client-1: Connected to 10.70.33.235:49182, attached to remote volume '/rajesh2/brick4'. [2015-05-19 10:43:45.203074] I [client-handshake.c:1474:client_setvolume_cbk] 0-vol1-client-1: Server and Client lk-version numbers are not same, reopening the fds [2015-05-19 10:43:45.205805] I [fuse-bridge.c:4977:fuse_graph_setup] 0-fuse: switched to graph 0 [2015-05-19 10:43:45.205884] I [client-handshake.c:450:client_set_lk_version_cbk] 0-vol1-client-1: Server lk version = 1 [2015-05-19 10:43:45.205895] I [client-handshake.c:450:client_set_lk_version_cbk] 0-vol1-client-0: Server lk version = 1 [2015-05-19 10:43:45.205946] I [fuse-bridge.c:3914:fuse_init] 0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.22 kernel 7.23 [2015-05-19 10:44:35.963145] I [glusterfsd.c:1959:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.5.2 (/usr/sbin/glusterfs --volfile-server=10.70.33.229 --volfile-id=/vol1/dir1/test /mnt/vol1) [2015-05-19 10:44:35.965688] I [socket.c:3561:socket_init] 0-glusterfs: SSL support is NOT enabled [2015-05-19 10:44:35.965710] I [socket.c:3576:socket_init] 0-glusterfs: using system polling thread [2015-05-19 10:44:36.042262] E [glusterfsd-mgmt.c:1297:mgmt_getspec_cbk] 0-glusterfs: failed to get the 'volume file' from server [2015-05-19 10:44:36.042317] E [glusterfsd-mgmt.c:1398:mgmt_getspec_cbk] 0-mgmt: failed to fetch volume file (key:/vol1/dir1/test) [2015-05-19 10:44:36.042487] W [glusterfsd.c:1095:cleanup_and_exit] (-->/lib64/libgfrpc.so.0(rpc_clnt_notify+0x171) [0x7ff22942da41] (-->/lib64/libgfrpc.so.0(rpc_clnt_handle_reply+0x90) [0x7ff22942d7c0] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x41d) [0x7ff229af7e3d]))) 0-: received signum (0), shutting down [2015-05-19 10:44:36.042499] I [fuse-bridge.c:5475:fini] 0-fuse: Unmounting '/mnt/vol1'. [2015-05-19 10:44:36.057326] W [glusterfsd.c:1095:cleanup_and_exit] (-->/lib64/libc.so.6(clone+0x6d) [0x7ff227e6477d] (-->/lib64/libpthread.so.0(+0x752a) [0x7ff22851552a] (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xe5) [0x7ff229af30d5]))) 0-: received signum (15), shutting down [2015-05-19 11:03:48.588327] W [socket.c:522:__socket_rwv] 0-glusterfs: readv on 10.70.33.229:24007 failed (Connection reset by peer) [2015-05-19 11:03:59.333577] I [glusterfsd-mgmt.c:1307:mgmt_getspec_cbk] 0-glusterfs: No change in volfile, continuing [root@rhs-client37 ~]# gluster vol status vol1 Status of volume: vol1 Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.33.229:/rajesh2/brick4 49185 0 Y 4291 Brick 10.70.33.235:/rajesh2/brick4 49182 0 Y 8511 NFS Server on localhost 2049 0 Y 4310 Bitrot Daemon on localhost N/A N/A Y 4318 Scrubber Daemon on localhost N/A N/A Y 4330 NFS Server on 10.70.33.235 2049 0 Y 8529 Bitrot Daemon on 10.70.33.235 N/A N/A Y 8537 Scrubber Daemon on 10.70.33.235 N/A N/A Y 8550 Task Status of Volume vol1 ------------------------------------------------------------------------------ There are no active volume tasks Expected results: ====================== Mount of sub directory should work properly Additional info:
Rajesh, This is the expected behaviour with gluster volume that is mounted using glusterfs native protocol. I believe you can selectively mount a directory with NFS Look at the option on the volume - nfs.export-volumes and nfs.export-dirs