Bug 1203648

Summary:	Quota: Build ancestry in the lookup
Product:	[Community] GlusterFS	Reporter:	Vijaikumar Mallikarjuna <vmallika>
Component:	sharding	Assignee:	Vijaikumar Mallikarjuna <vmallika>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6.2	CC:	bugs, rabhat, smohan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-v3.6.3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1184885	Environment:
Last Closed:	2016-02-04 15:20:35 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:
Embargoed:
Bug Depends On:	1184885, 1203589, 1222847
Bug Blocks:	1056085, 1184460, 1224138

Comment 1 Anand Avati 2015-03-19 10:47:48 UTC

REVIEW: http://review.gluster.org/9943 (Quota: Build ancestry in the lookup) posted (#1) for review on release-3.6 by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Anand Avati 2015-03-25 08:54:48 UTC

COMMIT: http://review.gluster.org/9943 committed in release-3.6 by Raghavendra Bhat (raghavendra) 
------
commit 0799f5f6091c09361fe0bc394fe614ee55d67296
Author: vmallika <vmallika>
Date:   Thu Mar 19 07:32:33 2015 +0530

    Quota: Build ancestry in the lookup
    
    This is a backport of http://review.gluster.org/#/c/9478/
    
    > Marker can fail or can account incorrect numbers when it doesn't find a
    > ancestry for a inode.
    >
    > Solution:
    > Current build_ancestry is done only on demand in the write/create FOPs
    > in quota enforcer.
    > It is good to do this in the quota_lookup as well.
    >
    > Change-Id: I8aaf5b3e05a3ca51e7ab1eaa1b636a90f659a872
    > BUG: 1184885
    > Signed-off-by: vmallika <vmallika>
    > Reviewed-on: http://review.gluster.org/9478
    > Tested-by: Gluster Build System <jenkins.com>
    > Reviewed-by: Raghavendra Bhat <raghavendra>
    > Reviewed-by: Vijay Bellur <vbellur>
    
    Change-Id: I57d3f801996da7194f5290067ff367888994786d
    BUG: 1203648
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/9943
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra Bhat <raghavendra>

Comment 3 Kaushal 2016-02-04 15:20:35 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-v3.6.3, please open a new bug report.

glusterfs-v3.6.3 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/2015-April/021669.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user