Bug 1259298 - Tier xattr name is misleading (trusted.tier-gfid)
Tier xattr name is misleading (trusted.tier-gfid)
Product: GlusterFS
Classification: Community
Component: tiering (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Nithya Balachandran
Depends On:
Blocks: 1273246 1273249
  Show dependency treegraph
Reported: 2015-09-02 07:41 EDT by Nithya Balachandran
Modified: 2016-06-16 09:34 EDT (History)
2 users (show)

See Also:
Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1273246 (view as bug list)
Last Closed: 2016-06-16 09:34:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nithya Balachandran 2015-09-02 07:41:38 EDT
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:

Actual results:

Expected results:

Additional info:
Comment 1 Vijay Bellur 2015-10-13 07:51:37 EDT
REVIEW: http://review.gluster.org/12350 (cluster/tier: Changed tier xattr-name value) posted (#1) for review on master by N Balachandran (nbalacha@redhat.com)
Comment 2 Vijay Bellur 2015-10-14 01:31:50 EDT
REVIEW: http://review.gluster.org/12350 (cluster/tier: Changed tier xattr-name value) posted (#2) for review on master by N Balachandran (nbalacha@redhat.com)
Comment 3 Vijay Bellur 2015-10-19 09:06:29 EDT
COMMIT: http://review.gluster.org/12350 committed in master by Dan Lambright (dlambrig@redhat.com) 
commit 0243085e40d842c59f4d7d59c61701ba416878ec
Author: N Balachandran <nbalacha@redhat.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.
    Change-Id: Id4adea61dc1c8473fb1d4d7364d1940278c6e129
    BUG: 1259298
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12350
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>
Comment 4 Niels de Vos 2016-06-16 09:34:51 EDT
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

Note You need to log in before you can comment on or make changes to this bug.