Bug 1283480

Summary:	Data Tiering:Rename of cold file to a hot file causing split brain and showing two copies of files in mount point
Product:	[Community] GlusterFS	Reporter:	Nithya Balachandran <nbalacha>
Component:	tiering	Assignee:	Nithya Balachandran <nbalacha>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.7.6	CC:	asrivast, bugs, dlambrig, nbalacha, nchilaka, rhs-bugs, sankarshan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1279376	Environment:
Last Closed:	2016-04-19 07:48:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1277088, 1279376
Bug Blocks:

Comment 1 Vijay Bellur 2015-11-19 05:53:49 UTC

REVIEW: http://review.gluster.org/12655 (cluster/tier: Do not delete linkto file on demotion) posted (#1) for review on release-3.7 by N Balachandran (nbalacha)

Comment 2 Vijay Bellur 2015-11-19 18:05:46 UTC

COMMIT: http://review.gluster.org/12655 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit 79103a0f9eea2af4c68710e602f78963471ecec7
Author: N Balachandran <nbalacha>
Date:   Mon Nov 9 15:49:50 2015 +0530

    cluster/tier: Do not delete linkto file on demotion
    
    The current DHT migration code will always delete the
    src linkto file after migration as dht always moves
     files to the hashed subvol. This is not the case in tiering.
    The lack of linkto files causes rename to fail leaving 2 files
     with the same name but different gfids on the volume.
    Modified to leave the linkto file behind if the source
     volume is the hashed subvolume.
    
    > Change-Id: I2b99f7d34b4b719aee6232dc40c6a8f8ba88225d
    > Signed-off-by: N Balachandran <nbalacha>
    > Reviewed-on: http://review.gluster.org/12551
    > Reviewed-by: Dan Lambright <dlambrig>
    > Tested-by: Dan Lambright <dlambrig>
    
    Change-Id: I210b94cdae0409c87af8ba198e3cd263a6c85190
    BUG: 1283480
    Signed-off-by: N Balachandran <nbalacha>
    Reviewed-on: http://review.gluster.org/12655
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Dan Lambright <dlambrig>

Comment 3 Kaushal 2016-04-19 07:48:31 UTC

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.7, please open a new bug report.

glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user