Bug 1294479 - quota: limit xattr not healed for a sub-directory on a newly added bricks
Summary: quota: limit xattr not healed for a sub-directory on a newly added bricks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Manikandan
QA Contact:
URL:
Whiteboard:
Depends On: 1294478
Blocks: 1294608
TreeView+ depends on / blocked
 
Reported: 2015-12-28 12:02 UTC by Vijaikumar Mallikarjuna
Modified: 2016-06-16 13:52 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1294478
: 1294608 (view as bug list)
Environment:
Last Closed: 2016-06-16 13:52:41 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Vijay Bellur 2015-12-28 12:07:24 UTC
REVIEW: http://review.gluster.org/13100 (quota: limit xattr for subdir not healed on newly added bricks) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Vijay Bellur 2015-12-29 16:28:17 UTC
COMMIT: http://review.gluster.org/13100 committed in master by Raghavendra G (rgowdapp) 
------
commit 72e736613169b778daa44e932443aaf2436432d9
Author: vmallika <vmallika>
Date:   Mon Dec 28 17:33:26 2015 +0530

    quota: limit xattr for subdir not healed on newly added bricks
    
    DHT after creating missing directory, tries to heal the
    xattrs. This xattrs operation fails as INTERNAL FOP key was not set
    
    Change-Id: I819d373cf7073da014143d9ada908228ddcd140c
    BUG: 1294479
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/13100
    Reviewed-by: Susant Palai <spalai>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra G <rgowdapp>
    Tested-by: NetBSD Build System <jenkins.org>

Comment 5 Niels de Vos 2016-06-16 13:52:41 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


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