Bug 1147953 - Enabling Quota on existing data won't create pgfid xattrs
Summary: Enabling Quota on existing data won't create pgfid xattrs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact:
URL:
Whiteboard:
Depends On: 1146830 1147378
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-30 11:53 UTC by Vijaikumar Mallikarjuna
Modified: 2016-05-11 22:48 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.6.1
Clone Of: 1147378
Environment:
Last Closed: 2014-11-10 15:13:56 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2014-09-30 11:55:07 UTC
REVIEW: http://review.gluster.org/8890 (glusterd/quota: Heal pgfid xattr on existing data when the quota is enable) posted (#2) for review on release-3.6 by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Anand Avati 2014-09-30 16:42:44 UTC
COMMIT: http://review.gluster.org/8890 committed in release-3.6 by Vijay Bellur (vbellur) 
------
commit 3dcb313572082edb07ed61145570b73a898c51e2
Author: vmallika <vmallika>
Date:   Mon Sep 29 13:02:30 2014 +0530

    glusterd/quota: Heal pgfid xattr on existing data when the quota is enable
    
    This is a backport of http://review.gluster.org/#/c/8878/
    
    The pgfid extended attributes are used to construct the ancestry path
    (from the file to the volume root) for nameless lookups on files.
    As NFS relies on nameless lookups heavily, quota enforcement through NFS
    would be inconsistent if quota were to be enabled on a volume with
    existing data.
    
    Solution is to heal the pgfid extended attributes as a part of lookup
    perfomed by quota-crawl process. In a posix lookup check for pgfid xattr
    and if it is missing set the xattr.
    
    BUG: 1147953
    Change-Id: I707d91a056e07452bfd1e070af5eddaa752a84ac
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/8890
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Niels de Vos 2014-11-10 15:13:56 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users


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