Description of problem: When sub-dir is mounted on Fuse client,adding bricks to the same volume unmounts the subdir on fuse client Version-Release number of selected component (if applicable): glusterfs-3.12.0 How reproducible: 2/2 Steps to Reproduce: 1.Create 4*3 Distributed-Replicate Volume 2.Mount the volume to glusterfs Fuse client 3.Create a directory inside the mount point say dir1 4.Set auth allow option on volume for dir1 # gluster v set ganeshavol1 auth.allow "/dir1(10.70.37.*),/(*)" volume set: success 5.Mount the sub-dir dir1 on the same client 6.Start creating 512 kb of files inside sub-dir mount point 7.when IO's are in process,add 3 bricks to existing volume Actual results: Brick add operation passed on volume.After bricks are added,sub-dir is automatically unmounted from the fuse client. Expected results: Add brick operation should not unmount the sub-dir from fuse client. Additional info: brick logs on newly added bricks- 1-client-12-2-0 (version: 3.8.4) [2017-10-18 04:24:38.619538] E [server-handshake.c:342:do_path_lookup] 0-/gluster/brick5/b1: first lookup on subdir (dir1) failed: Success [2017-10-18 04:24:38.619554] E [server-handshake.c:402:server_first_lookup] 0-ganeshavol1-server: first lookup on subdir (/dir1) failed: Invalid argument Cliemt logs- # cat mnt-Fuse-Subdir.log | grep E [2017-10-18 04:22:26.816447] I [fuse-bridge.c:4153:fuse_init] 0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.24 kernel 7.22 [2017-10-18 04:24:38.613427] E [MSGID: 114044] [client-handshake.c:1139:client_setvolume_cbk] 2-ganeshavol1-client-12: SETVOLUME on remote-host failed: subdirectory for mount "/dir1" is not found [No such file or directory] [2017-10-18 04:24:38.613441] I [MSGID: 114049] [client-handshake.c:1249:client_setvolume_cbk] 2-ganeshavol1-client-12: sending AUTH_FAILED event [2017-10-18 04:24:38.613462] E [fuse-bridge.c:5328:notify] 0-fuse: Server authenication failed. Shutting down.
REVIEW: https://review.gluster.org/18550 (protocol/client: handle the subdir handshake properly for add-brick) posted (#3) for review on master by Amar Tumballi (amarts)
REVIEW: https://review.gluster.org/18550 (protocol/client: handle the subdir handshake properly for add-brick) posted (#4) for review on master by Amar Tumballi (amarts)
REVIEW: https://review.gluster.org/18550 (protocol/client: handle the subdir handshake properly for add-brick) posted (#5) for review on master by Amar Tumballi (amarts)
COMMIT: https://review.gluster.org/18550 committed in master by Amar Tumballi (amarts) ------ commit 9aa574a51b84717c1f3949ed2e28a49e49840a93 Author: Amar Tumballi <amarts> Date: Sun Oct 22 12:41:38 2017 +0530 protocol/client: handle the subdir handshake properly for add-brick There should be different way we handle handshake in case of subdir mount for the first time, and in case of subsequent graph changes. Change-Id: I2a7ba836433bb0a0f4a861809e2bb0d7fbc4da54 BUG: 1505323 Signed-off-by: Amar Tumballi <amarts>
COMMIT: https://review.gluster.org/18550 committed in master by \n\n -------------\n\n protocol/client: handle the subdir handshake properly for add-brick There should be different way we handle handshake in case of subdir mount for the first time, and in case of subsequent graph changes. Change-Id: I2a7ba836433bb0a0f4a861809e2bb0d7fbc4da54 BUG: 1505323 Signed-off-by: Amar Tumballi <amarts>
COMMIT: https://review.gluster.org/18550 committed in master by ------------- protocol/client: handle the subdir handshake properly for add-brick There should be different way we handle handshake in case of subdir mount for the first time, and in case of subsequent graph changes. Change-Id: I2a7ba836433bb0a0f4a861809e2bb0d7fbc4da54 BUG: 1505323 Signed-off-by: Amar Tumballi <amarts>
REVIEW: https://review.gluster.org/18586 (protocol/client: handle the subdir handshake properly for add-brick) posted (#1) for review on release-3.12 by Amar Tumballi
COMMIT: https://review.gluster.org/18586 committed in release-3.12 by ------------- protocol/client: handle the subdir handshake properly for add-brick There should be different way we handle handshake in case of subdir mount for the first time, and in case of subsequent graph changes. Change-Id: I2a7ba836433bb0a0f4a861809e2bb0d7fbc4da54 BUG: 1505323 Signed-off-by: Amar Tumballi <amarts> (cherry picked from commit 9aa574a51b84717c1f3949ed2e28a49e49840a93)
glusterfs-3.12.3 has the fix
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-glusterfs-3.12.3, please open a new bug report. glusterfs-glusterfs-3.12.3 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-devel/2017-November/053983.html [2] https://www.gluster.org/pipermail/gluster-users/
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.13.0, please open a new bug report. glusterfs-3.13.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/