Description of problem: When doing some write operations to a dispersed volume (for example an untar), sometimes the client crashes and the error "Transport endpoint is not connected" is returned. Version-Release number of selected component (if applicable): mainline How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: This seems to be caused by an incorrect destruction of inode context information on inode invalidate notifications.
REVIEW: http://review.gluster.org/8420 (ec: Do not destroy inode context on inode invalidation) posted (#1) for review on master by Xavier Hernandez (xhernandez)
COMMIT: http://review.gluster.org/8420 committed in master by Vijay Bellur (vbellur) ------ commit 51becaa5e803bd21807f30524da58a578061541b Author: Xavier Hernandez <xhernandez> Date: Tue Aug 5 18:28:25 2014 +0200 ec: Do not destroy inode context on inode invalidation Currently there is no need to handle inode invalidation requests, so this callback has been removed. Change-Id: I0ac2e47679bf62b1493e0403178305923bc036e8 BUG: 1126932 Signed-off-by: Xavier Hernandez <xhernandez> Reviewed-on: http://review.gluster.org/8420 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Jeff Darcy <jdarcy> Reviewed-by: Dan Lambright <dlambrig> 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