REVIEW: http://review.gluster.org/13330 (USS: pre-existing .snaps should not be listed with 'ls -a' with USS enabled) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/13330 (USS: pre-existing .snaps should not be listed with 'ls -a' with USS enabled) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/13330 (USS: pre-existing .snaps should not be listed with 'ls -a' with USS enabled) posted (#3) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/13330 (USS: pre-existing .snaps should not be listed with 'ls -a' with USS enabled) posted (#4) for review on master by Vijaikumar Mallikarjuna (vmallika)
COMMIT: http://review.gluster.org/13330 committed in master by Rajesh Joseph (rjoseph) ------ commit 954f2901345f42177033418112c052ed0795b295 Author: vmallika <vmallika> Date: Tue Feb 2 12:30:16 2016 +0530 USS: pre-existing .snaps should not be listed with 'ls -a' with USS enabled If there is a .snaps directory pre-exists and when USS is enabled, it should not be listed with 'ls -a' Change-Id: I1c43e2decc0bbbd3213b190b675e3a32d04b22d3 BUG: 1303828 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/13330 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Rajesh Joseph <rjoseph>
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user