Bug 1251121

Summary:	Unable to demote files in tiered volumes when cold tier is EC.
Product:	[Community] GlusterFS	Reporter:	Dan Lambright <dlambrig>
Component:	tiering	Assignee:	Dan Lambright <dlambrig>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, vagarwal
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1252907 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:29:42 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:
Bug Blocks:	1252907, 1260923

Description Dan Lambright 2015-08-06 13:28:44 UTC

Unable to demote files in tiered volumes when cold tier is EC.

Comment 1 Anand Avati 2015-08-06 14:06:47 UTC

REVIEW: http://review.gluster.org/11855 (cluster/tier: fix demotion when cold tier is EC) posted (#1) for review on master by Dan Lambright (dlambrig)

Comment 2 Anand Avati 2015-08-11 19:35:48 UTC

REVIEW: http://review.gluster.org/11855 (cluster/tier: fix demotion when cold tier is EC) posted (#2) for review on master by Dan Lambright (dlambrig)

Comment 3 Anand Avati 2015-08-12 11:49:11 UTC

COMMIT: http://review.gluster.org/11855 committed in master by Dan Lambright (dlambrig) 
------
commit e65160c5bec78e7385eedf3cf02d9cdcb756db0c
Author: Dan Lambright <dlambrig>
Date:   Thu Aug 6 09:59:35 2015 -0400

    cluster/tier: fix demotion when cold tier is EC
    
    We did not set the gfid in the loc structure in tier demotion. EC
    has a sanity check which fails FOPs when the loc gfid mismatches
    with the file attribute. When the FOP failed demotion was aborted.
    
    Change-Id: I69022c9ccb135b86e1feea93b01801b6a4100509
    BUG: 1251121
    Signed-off-by: Dan Lambright <dlambrig>
    Reviewed-on: http://review.gluster.org/11855
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: mohammed rafi  kc <rkavunga>
    Reviewed-by: Venky Shankar <vshankar>

Comment 4 Nagaprasad Sathyanarayana 2015-10-25 15:16:49 UTC

Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 5 Niels de Vos 2016-06-16 13:29:42 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.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user