REVIEW: https://review.gluster.org/17465 (gfapi: change root lookup from nameless to named lookup) posted (#1) for review on master by mohammed rafi kc (rkavunga)
REVIEW: https://review.gluster.org/17465 (gfapi: change root lookup from nameless to named lookup) posted (#2) for review on master by mohammed rafi kc (rkavunga)
REVIEW: https://review.gluster.org/17465 (gfapi: change root lookup from nameless to named lookup) posted (#3) for review on master by mohammed rafi kc (rkavunga)
REVIEW: https://review.gluster.org/17465 (gfapi: change root lookup from nameless to named lookup) posted (#4) for review on master by mohammed rafi kc (rkavunga)
REVIEW: https://review.gluster.org/17465 (gfapi: change root lookup from nameless to named lookup) posted (#5) for review on master by mohammed rafi kc (rkavunga)
COMMIT: https://review.gluster.org/17465 committed in master by Niels de Vos (ndevos) ------ commit d95aa04e482ebe4306df721fe0aa3697a0426a85 Author: Mohammed Rafi KC <rkavunga> Date: Fri Jun 2 16:28:40 2017 +0530 gfapi: change root lookup from nameless to named lookup Problem: During component resolve we do lookup on root based on root gfid. If we are doing nameless lookup, then md-cache won't be able to serve those lookup. Solution: With this patch, we covert nameless lookup to named lookup on root. Credits: Poornima G <pgurusid> Change-Id: Ie64141936fd294d8969c39e3bd4dbc73ee375c6b BUG: 1458768 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: https://review.gluster.org/17465 Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Niels de Vos <ndevos>
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.12.0, please open a new bug report. glusterfs-3.12.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://lists.gluster.org/pipermail/announce/2017-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/