+++ This bug was initially created as a clone of Bug #1126932 +++ 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. --- Additional comment from Anand Avati on 2014-08-05 18:30:47 CEST --- 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)
REVIEW: http://review.gluster.org/8702 (ec: Do not destroy inode context on inode invalidation) posted (#1) for review on release-3.6 by Xavier Hernandez (xhernandez)
COMMIT: http://review.gluster.org/8702 committed in release-3.6 by Vijay Bellur (vbellur) ------ commit 5b6ebde7fade37d2c261898ccc917abf16cc520a 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. This is a backport of http://review.gluster.org/8420/ Change-Id: I0ac2e47679bf62b1493e0403178305923bc036e8 BUG: 1140846 Signed-off-by: Xavier Hernandez <xhernandez> Reviewed-on: http://review.gluster.org/8702 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
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