Bug 1293342

Summary:	Data Tiering:Watermark:File continuously trying to demote itself but failing " [dht-rebalance.c:608:__dht_rebalance_create_dst_file] 0-wmrk-tier-dht: chown failed for //AP.BH.avi on wmrk-cold-dht (No such file or directory)"
Product:	[Community] GlusterFS	Reporter:	Mohammed Rafi KC <rkavunga>
Component:	tiering	Assignee:	Mohammed Rafi KC <rkavunga>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.6	CC:	aspandey, bugs, dlambrig, nbalacha, nchilaka, 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:	1292067	Environment:
Last Closed:	2016-04-19 07:51:49 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:	1286218, 1292067
Bug Blocks:

Comment 1 Vijay Bellur 2015-12-21 13:44:24 UTC

REVIEW: http://review.gluster.org/13045 (tier: Demotion failed if the file was renamed when it was in cold) posted (#1) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 2 Vijay Bellur 2015-12-30 16:29:09 UTC

COMMIT: http://review.gluster.org/13045 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit 7d84f8b95ecfa4f3d68eb0cbe7bd18f4293ec441
Author: Mohammed Rafi KC <rkavunga>
Date:   Wed Dec 16 17:16:36 2015 +0530

    tier: Demotion failed if the file was renamed when it was in cold
    
    During migration if the file is present we just open the file
    in hashed subvol. Now if the linkfile present on hashed is just
    linkfile to another subvol, we actually open in hashed subvol.
    
    But subsequent operation will go to linkto subvol ie,
    to non-hashed subvol. This operation will get failed
    since we haven't opened d on non-hashed.
    
    Backport of>
    >Change-Id: I9753ad3a48f0384c25509612ba76e7e10645add3
    >BUG: 1292067
    >Signed-off-by: Mohammed Rafi KC <rkavunga>
    >Reviewed-on: http://review.gluster.org/12980
    >Tested-by: NetBSD Build System <jenkins.org>
    >Reviewed-by: Susant Palai <spalai>
    >Tested-by: Gluster Build System <jenkins.com>
    >Reviewed-by: Dan Lambright <dlambrig>
    >Tested-by: Dan Lambright <dlambrig>
    
    (cherry picked from commit d2f48214d436be633efb1136ee951b0736935143)
    
    
    Change-Id: I562ac4ba73e6b572bc1be91e55a029fa75262b33
    BUG: 1293342
    Signed-off-by: Mohammed Rafi KC <rkavunga>
    Reviewed-on: http://review.gluster.org/13045
    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:51:49 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