Description of problem:
In some circumstances, when healing a file, glusterfs crashes
Version-Release number of selected component (if applicable): 3.6
It happens sometimes. Not sure how to force it.
Steps to Reproduce:
REVIEW: http://review.gluster.org/8368 (ec: Only heal data/metadata when inode has enough information) posted (#1) for review on master by Xavier Hernandez (email@example.com)
COMMIT: http://review.gluster.org/8368 committed in master by Vijay Bellur (firstname.lastname@example.org)
Author: Xavier Hernandez <email@example.com>
Date: Tue Jul 15 13:42:28 2014 +0200
ec: Only heal data/metadata when inode has enough information
Sometimes loc_t structure in a heal request doesn't contain enough
information to do an inodelk call (basically the gfid is missing).
In these cases, self heal only recovers entry information.
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>
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.