REVIEW: http://review.gluster.org/9306 (gluster/uss: Don't send failure when accessing snap with name same as entry-point name) posted (#1) for review on release-3.6 by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/9306 (gluster/uss: Don't send failure when accessing snap with name same as entry-point name.) posted (#2) for review on release-3.6 by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/9306 (gluster/uss: Don't send failure when accessing snap with name same as entry-point name) posted (#3) for review on release-3.6 by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/9306 (gluster/uss: Don't send failure when accessing snap with name same as entry-point name.) posted (#4) for review on release-3.6 by Sachin Pandit (spandit)
COMMIT: http://review.gluster.org/9306 committed in release-3.6 by Raghavendra Bhat (raghavendra) ------ commit 5a3f91bc2140a53e1e6a7d98aed939a01f18f034 Author: vmallika <vmallika> Date: Mon Nov 17 07:14:28 2014 +0530 gluster/uss: Don't send failure when accessing snap with name same as entry-point name. In a scenario, if the snap name is same as the snap-directory than cd to snaps/snaps fails. Send a lookup to snap-view server instead of failing Change-Id: Ie7b811815ff30961500592bbc8cdb514a9d76ef5 BUG: 1175733 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/9135 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Rajesh Joseph <rjoseph> Reviewed-by: Avra Sengupta <asengupt> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas> Signed-off-by: Sachin Pandit <spandit> Reviewed-on: http://review.gluster.org/9306 Reviewed-by: Raghavendra Bhat <raghavendra>
Description of problem: ======================= In a scenario, if the snap name is same as the snap-directory than cd to snaps/snaps fails. For example: ============ The snap directory is changed to snaps as follows [root@inception ~]# gluster v set vol0 snapshot-directory snaps volume set: success [root@inception ~]# Snapshot is created with name snaps [root@inception ~]# gluster snapshot create snaps vol0 snapshot create: success: Snap snaps created successfully [root@inception ~]# From client cd to snaps/snaps from fuse client fails [root@wingo ~]# cd /mnt/vol0 [root@wingo vol0]# [root@wingo vol0]# cd snaps/snaps bash: cd: snaps/snaps: No such file or directory [root@wingo vol0]# cd snaps/ [root@wingo snaps]# ls snaps [root@wingo snaps]# ls snaps ls: cannot access snaps: No such file or directory [root@wingo snaps]# ls -lrt snaps ls: cannot access snaps: No such file or directory [root@wingo snaps]# ls -lrt total 0 d---------. 0 root root 0 Jan 1 1970 snaps [root@wingo snaps]# Version-Release number of selected component (if applicable): ============================================================== glusterfs-3.6.0.32-1.el6rhs.x86_64 How reproducible: ================= always Steps to Reproduce: ==================== 1. Create 2x2 volume 2. Enable the uss on volume 3. Change the snapshot-directory to snaps 4. Create a snapshot (snaps) of the volume 5. Mount the volume (fuse) 6. From mount, cd to snaps/snaps Actual results: =============== cd to snaps/snaps fails with no such file or directory. Though ls lists it.
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.6.2, please reopen this bug report. glusterfs-3.6.2 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should already be or become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. The fix for this bug likely to be included in all future GlusterFS releases i.e. release > 3.6.2. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/5978 [2] http://news.gmane.org/gmane.comp.file-systems.gluster.user [3] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137