REVIEW: http://review.gluster.org/9998 (Cluster/DHT Mismatching gfid values in dht_local_t) posted (#1) for review on master by N Balachandran (nbalacha)
The issue is seen because dht_linkfile_create() uses the gfid in local->gfid and dht_linkfile_attr_heal() uses the value in local->stbuf.gfid. In a situation where duplicate files with different gfids are present on the bricks (because of another bug), these values do not match, causing the failure as the linkfile is created with one gfid but the attr_heal is done with the other gfid.
REVIEW: http://review.gluster.org/9998 (Cluster/DHT Mismatching gfid values in dht_local_t) posted (#2) for review on master by N Balachandran (nbalacha)
REVIEW: http://review.gluster.org/9998 (Cluster/DHT Mismatching gfid values in dht_local_t) posted (#3) for review on master by N Balachandran (nbalacha)
REVIEW: http://review.gluster.org/9998 (Cluster/DHT Mismatching gfid values in dht_local_t) posted (#4) for review on master by N Balachandran (nbalacha)
REVIEW: http://review.gluster.org/9998 (Cluster/DHT Mismatching gfid values in dht_local_t) posted (#5) for review on master by N Balachandran (nbalacha)
COMMIT: http://review.gluster.org/9998 committed in master by Shyamsundar Ranganathan (srangana) ------ commit a7f1d08b8f0bdf8d251590d6f7e4acc46f2486b4 Author: Nithya Balachandran <nbalacha> Date: Wed Mar 25 21:07:36 2015 +0530 Cluster/DHT Mismatching gfid values in dht_local_t If multiple files with the same name but different gfids exist on different subvolumes, dht_lookup_everywhere_cbk() copies the gfid from the last received response into local->gfid but does not update the local->stbuf structure. dht_linkfile_create() uses the value in local->gfid, but dht_linkfile_attr_heal() uses the one in local->stbuf, causing a mismatch and failure while trying to heal the linkfile attrs. Change-Id: I80d152be95b42d736c5d9182b955f42e374b82a5 BUG: 1205785 Signed-off-by: Nithya Balachandran <nbalacha> Reviewed-on: http://review.gluster.org/9998 Reviewed-by: Susant Palai <spalai> Reviewed-by: Shyamsundar Ranganathan <srangana> Tested-by: Shyamsundar Ranganathan <srangana>
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