Description of problem: In some circumstances, when healing a file, glusterfs crashes Version-Release number of selected component (if applicable): 3.6 How reproducible: It happens sometimes. Not sure how to force it. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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 (xhernandez)
COMMIT: http://review.gluster.org/8368 committed in master by Vijay Bellur (vbellur) ------ commit 2be54585002cd1c9d02928b89a02047b58dd6aed Author: Xavier Hernandez <xhernandez> 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. Change-Id: I459990c7df728ff4baf164df046672ddcde3efa5 BUG: 1122581 Signed-off-by: Xavier Hernandez <xhernandez> Reviewed-on: http://review.gluster.org/8368 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Jeff Darcy <jdarcy> Reviewed-by: Dan Lambright <dlambrig>
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