Bug 1259298

Summary:	Tier xattr name is misleading (trusted.tier-gfid)
Product:	[Community] GlusterFS	Reporter:	Nithya Balachandran <nbalacha>
Component:	tiering	Assignee:	Nithya Balachandran <nbalacha>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, sankarshan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1273246 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:34:51 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:	1273246, 1273249

Description Nithya Balachandran 2015-09-02 11:41:38 UTC

Description of problem:
The trusted.tier-gfid xattr does not actually store a gfid.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2015-10-13 11:51:37 UTC

REVIEW: http://review.gluster.org/12350 (cluster/tier: Changed tier xattr-name value) posted (#1) for review on master by N Balachandran (nbalacha)

Comment 2 Vijay Bellur 2015-10-14 05:31:50 UTC

REVIEW: http://review.gluster.org/12350 (cluster/tier: Changed tier xattr-name value) posted (#2) for review on master by N Balachandran (nbalacha)

Comment 3 Vijay Bellur 2015-10-19 13:06:29 UTC

COMMIT: http://review.gluster.org/12350 committed in master by Dan Lambright (dlambrig) 
------
commit 0243085e40d842c59f4d7d59c61701ba416878ec
Author: N Balachandran <nbalacha>
Date:   Tue Oct 13 17:11:29 2015 +0530

    cluster/tier: Changed tier xattr-name value
    
    Each tier layer (for future stacking implementations)
    must have a unique xattr name. We are currently using
    the name of the tier subvolume excluding the volume name.
    
    Change-Id: Id4adea61dc1c8473fb1d4d7364d1940278c6e129
    BUG: 1259298
    Signed-off-by: N Balachandran <nbalacha>
    Reviewed-on: http://review.gluster.org/12350
    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 4 Niels de Vos 2016-06-16 13:34:51 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