Bug 1302257 - [tiering]: Quota object limits not adhered to, in a tiered volume
Summary: [tiering]: Quota object limits not adhered to, in a tiered volume
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: All
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Manikandan
QA Contact:
URL:
Whiteboard:
Depends On: 1300307
Blocks: 1306138
TreeView+ depends on / blocked
 
Reported: 2016-01-27 10:14 UTC by Manikandan
Modified: 2016-06-16 13:56 UTC (History)
5 users (show)

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

Attachments (Terms of Use)

Comment 1 Vijay Bellur 2016-01-27 10:16:43 UTC 
REVIEW: http://review.gluster.org/13299 (dht/quota : heal the limit_objects_key xattr needed for inode-quota) posted (#1) for review on master by Manikandan Selvaganesh (mselvaga)
Comment 2 Vijay Bellur 2016-01-27 19:33:44 UTC 
REVIEW: http://review.gluster.org/13299 (dht/quota : heal the limit_objects_key xattr needed for inode-quota) posted (#2) for review on master by Manikandan Selvaganesh (mselvaga)
Comment 3 Vijay Bellur 2016-01-28 05:33:01 UTC 
REVIEW: http://review.gluster.org/13299 (dht/quota : heal the limit_objects_key xattr needed for inode-quota) posted (#3) for review on master by Manikandan Selvaganesh (mselvaga)
Comment 4 Vijay Bellur 2016-02-01 10:43:43 UTC 
REVIEW: http://review.gluster.org/13299 (dht/quota : heal the limit_objects_key xattr needed for inode-quota) posted (#4) for review on master by Manikandan Selvaganesh (mselvaga)
Comment 5 Vijay Bellur 2016-02-02 12:20:05 UTC 
REVIEW: http://review.gluster.org/13299 (dht/quota : heal the limit_objects_key xattr needed for inode-quota) posted (#5) for review on master by Manikandan Selvaganesh (mselvaga)
Comment 6 Vijay Bellur 2016-02-09 13:08:32 UTC 
REVIEW: http://review.gluster.org/13299 (dht/quota : heal the limit_objects_key xattr needed for inode-quota) posted (#6) for review on master by Manikandan Selvaganesh (mselvaga)
Comment 7 Vijay Bellur 2016-02-10 06:34:23 UTC 
REVIEW: http://review.gluster.org/13299 (dht/quota : heal the limit_objects_key xattr needed for inode-quota) posted (#7) for review on master by Manikandan Selvaganesh (mselvaga)
Comment 8 Vijay Bellur 2016-02-11 05:21:34 UTC 
COMMIT: http://review.gluster.org/13299 committed in master by Raghavendra G (rgowdapp) 
------
commit acfb402414ec4a9ab8c9f9d4fead6b9141c2e934
Author: Manikandan Selvaganesh <mselvaga>
Date:   Wed Jan 27 14:56:33 2016 +0530

    dht/quota : heal the limit_objects_key xattr needed for inode-quota
    
    Whenever a new brick is added, quota related xattr's
    should be healed but currently, the xattr
    "quota.limit-objects.<suffix>" needed for inode-quota is
    not being healed.
    The patch fixes this issue.
    
    Change-Id: I1e7b229126f7b058642bbc3fb5c109bfd8925325
    BUG: 1302257
    Signed-off-by: Manikandan Selvaganesh <mselvaga>
    Reviewed-on: http://review.gluster.org/13299
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika>
    Reviewed-by: Raghavendra G <rgowdapp>
Comment 9 Niels de Vos 2016-06-16 13:56:06 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.