Red Hat Bugzilla – Bug 1259298
Tier xattr name is misleading (trusted.tier-gfid)
Last modified: 2016-06-16 09:34:51 EDT
Description of problem:
The trusted.tier-gfid xattr does not actually store a gfid.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: http://review.gluster.org/12350 (cluster/tier: Changed tier xattr-name value) posted (#1) for review on master by N Balachandran (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/12350 (cluster/tier: Changed tier xattr-name value) posted (#2) for review on master by N Balachandran (email@example.com)
COMMIT: http://review.gluster.org/12350 committed in master by Dan Lambright (firstname.lastname@example.org)
Author: N Balachandran <email@example.com>
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.
Signed-off-by: N Balachandran <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Tested-by: NetBSD Build System <firstname.lastname@example.org>
Reviewed-by: Dan Lambright <email@example.com>
Tested-by: Dan Lambright <firstname.lastname@example.org>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.