REVIEW: http://review.gluster.org/6500 (dht: do not remove linkfile if file exist in cached sub volume) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/6500 (dht: do not remove linkfile if file exist in cached sub volume) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/6500 (dht: do not remove linkfile if file exist in cached sub volume) posted (#3) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/6500 (dht: do not remove linkfile if file exist in cached sub volume) posted (#4) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/6500 (dht: do not remove linkfile if file exist in cached sub volume) posted (#5) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/6500 (dht: do not remove linkfile if file exist in cached sub volume) posted (#6) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/6500 (dht: do not remove linkfile if file exist in cached sub volume) posted (#7) for review on master by Vijaikumar Mallikarjuna (vmallika)
COMMIT: http://review.gluster.org/6500 committed in master by Anand Avati (avati) ------ commit 3023a50c1410b4da457e86bed69c320760d37344 Author: Vijaykumar M <vmallika> Date: Fri Dec 13 14:18:16 2013 +0530 dht: do not remove linkfile if file exist in cached sub volume Currently with rmdir, if a directory contains only the linkfiles we remove all the linkfiles and this is causing the problem when the cached sub volume is down and end-up with duplicate files showing on the mount point. Solution: Before removing a linkfile check if the files exists in cached subvolume. Change-Id: Iedffd0d9298ec8bb95d5ce27c341c9ade81f0d3c BUG: 1042725 Signed-off-by: Vijaykumar M <vmallika> Reviewed-on: http://review.gluster.org/6500 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users