REVIEW: http://review.gluster.org/9153 (gluster/uss: Handle ESTALE in snapview client when NFS server restarted) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9153 (gluster/uss: Handle ESTALE in snapview client when NFS server restarted) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9153 (gluster/uss: Handle ESTALE in snapview client when NFS server restarted) posted (#3) for review on master by Vijaikumar Mallikarjuna (vmallika)
COMMIT: http://review.gluster.org/9153 committed in master by Vijay Bellur (vbellur) ------ commit 8277f4e4a4e92543ac139ef63d0ad82add397de7 Author: vmallika <vmallika> Date: Thu Nov 20 20:36:00 2014 +0530 gluster/uss: Handle ESTALE in snapview client when NFS server restarted When NFS server is restarted inode-context is lost. Nameless lookup will be sent to regular volume. If the gfid is from virtual graph, lookup will fail with ESTALE. We need to send a lookup to snapview server Change-Id: I22920614f0d14cb90b53653fce95b6b70023eba6 BUG: 1166197 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/9153 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Sachin Pandit <spandit> 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