REVIEW: http://review.gluster.org/9205 (gluster/uss: Handle notify in snapview-client) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9205 (gluster/uss: Handle notify in snapview-client) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)
COMMIT: http://review.gluster.org/9205 committed in master by Vijay Bellur (vbellur) ------ commit d6278602caabac85b49887dc45e83b3cadfeb19b Author: vmallika <vmallika> Date: Thu Nov 27 18:38:59 2014 +0530 gluster/uss: Handle notify in snapview-client As there are two subvolumes in snapview-client, there is a possibility that the regular subvolume is still down and snapd subvolume come up first. So if we don't handle this situation CHILD_UP event will be propagated upwards to fuse when regular subvolume is still down. This can cause data unavailable for the application Change-Id: I9e5166ed22c2cf637c15db0457c2b57ca044078e BUG: 1168643 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/9205 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user