Bug 1312954

Summary: quota: xattr trusted.glusterfs.quota.limit-objects not healed on a root of newly added brick
Product: [Community] GlusterFS Reporter: Vijaikumar Mallikarjuna <vmallika>
Component: quotaAssignee: Vijaikumar Mallikarjuna <vmallika>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.7.8CC: amukherj, bugs, fharshav, smohan, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1306220 Environment:
Last Closed: 2016-04-19 07:22:11 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:
Bug Depends On: 1306218, 1306220    
Bug Blocks:    

Comment 1 Vijay Bellur 2016-02-29 15:46:58 UTC
REVIEW: http://review.gluster.org/13551 (quota: heal object-limit on a root dir of a newly added brick) posted (#1) for review on release-3.7 by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Vijay Bellur 2016-03-04 06:15:43 UTC
COMMIT: http://review.gluster.org/13551 committed in release-3.7 by Atin Mukherjee (amukherj) 
------
commit 1da6a7525eb83f429c6f6ef2bba58c0adf3f64aa
Author: vmallika <vmallika>
Date:   Wed Feb 10 16:27:05 2016 +0530

    quota: heal object-limit on a root dir of a newly added brick
    
    This is a backport of http://review.gluster.org/13422
    
    When a new brick is added, xattr trusted.glusterfs.quota.limit-objects
    is not healed on a root directory.
    This patch will fix the problem
    
    > Change-Id: I776609ebf4d7822c541b6262e63d465ea3a86db4
    > BUG: 1306220
    > Signed-off-by: vmallika <vmallika>
    > Reviewed-on: http://review.gluster.org/13422
    > Smoke: Gluster Build System <jenkins.com>
    > CentOS-regression: Gluster Build System <jenkins.com>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > Reviewed-by: Atin Mukherjee <amukherj>
    
    Change-Id: I47412b4da35c0f5d28106020daf32212d267cb9e
    BUG: 1312954
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/13551
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 3 Kaushal 2016-04-19 07:22:11 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.7.9, please open a new bug report.

glusterfs-3.7.9 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] https://www.gluster.org/pipermail/gluster-users/2016-March/025922.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user