Bug 1317366

Summary:	Tier: Actual files are not demoted and keep on trying to demoted deleted files
Product:	[Community] GlusterFS	Reporter:	hari gowtham <hgowtham>
Component:	tiering	Assignee:	hari gowtham <hgowtham>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.9	CC:	bugs, dlambrig, nchilaka, rmekala
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	tier-migration
Fixed In Version:	glusterfs-3.7.10	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1311178	Environment:
Last Closed:	2016-04-19 06:59:50 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:	1296908, 1311178
Bug Blocks:

Comment 1 Vijay Bellur 2016-03-14 06:36:18 UTC

REVIEW: http://review.gluster.org/13692 (Tier: Avoiding stale entries from causing demotion to stop) posted (#1) for review on release-3.7 by hari gowtham (hari.gowtham005)

Comment 2 Vijay Bellur 2016-03-17 05:25:16 UTC

REVIEW: http://review.gluster.org/13692 (Tier: Avoiding stale entries from causing demotion to stop) posted (#2) for review on release-3.7 by hari gowtham (hari.gowtham005)

Comment 3 Vijay Bellur 2016-03-22 09:06:53 UTC

COMMIT: http://review.gluster.org/13692 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit 84d378dcb3cfae9e643eb548e9861cfb274df15e
Author: hari gowtham <hgowtham>
Date:   Tue Feb 23 20:09:52 2016 +0530

    Tier: Avoiding stale entries from causing demotion to stop
    
        back-port of : http://review.gluster.org/#/c/13501/
    
    When the parent GFID is a stale entry, the lookup on this parent
    fails and this in turn fails the demotion process.
    
    This patch will make the stale entry error to be skipped.
    
    Situation for pargfid to be stale:
    Consider a folder from a tar file. Once the tar file is untared
    the files in the tar-file will start to demote.
    when the demotion is under progress, if we tend to delete
    the actual folder, then the files under it which are
    undergoing demotion will do a lookup on the parent which was
    deleted and become stale entry. This stale entry fails the
    Lookup and this will fail the demotion of the other files(not from
    tar) that are supposed to be demoted.
    
    >Change-Id: I3d47c32c4077526d477a25912b0135bab98b23fc
    >BUG: 1311178
    >Signed-off-by: hari gowtham <hgowtham>
    >Reviewed-on: http://review.gluster.org/13501
    >Tested-by: hari gowtham <hari.gowtham005>
    >Smoke: Gluster Build System <jenkins.com>
    >CentOS-regression: Gluster Build System <jenkins.com>
    >Reviewed-by: Dan Lambright <dlambrig>
    >NetBSD-regression: NetBSD Build System <jenkins.org>
    
    Change-Id: I80a77d149180e2a05b3d7943f370b3ef162e545b
    BUG: 1317366
    Signed-off-by: Hari Gowtham <hgowtham>
    Reviewed-on: http://review.gluster.org/13692
    Smoke: Gluster Build System <jenkins.com>
    Tested-by: hari gowtham <hari.gowtham005>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>

Comment 4 Kaushal 2016-04-19 06:59:50 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.10, please open a new bug report.

glusterfs-3.7.10 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-April/026164.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user