REVIEW: http://review.gluster.org/9943 (Quota: Build ancestry in the lookup) posted (#1) for review on release-3.6 by Vijaikumar Mallikarjuna (email@example.com)
COMMIT: http://review.gluster.org/9943 committed in release-3.6 by Raghavendra Bhat (firstname.lastname@example.org)
Author: vmallika <email@example.com>
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.
> 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 <firstname.lastname@example.org>
> Reviewed-on: http://review.gluster.org/9478
> Tested-by: Gluster Build System <email@example.com>
> Reviewed-by: Raghavendra Bhat <firstname.lastname@example.org>
> Reviewed-by: Vijay Bellur <email@example.com>
Signed-off-by: vmallika <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Raghavendra Bhat <firstname.lastname@example.org>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.