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
Steps to Reproduce:
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 (email@example.com)
COMMIT: http://review.gluster.org/8420 committed in master by Vijay Bellur (firstname.lastname@example.org)
Author: Xavier Hernandez <email@example.com>
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.
Signed-off-by: Xavier Hernandez <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Jeff Darcy <firstname.lastname@example.org>
Reviewed-by: Dan Lambright <email@example.com>
Reviewed-by: Vijay Bellur <firstname.lastname@example.org>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.