REVIEW: http://review.gluster.org/11431 (tiering/quota: failed to match subvolume) posted (#2) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/11459 (ctr:Avoid assertion failure in lookup) posted (#1) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/11459 (ctr:Avoid assertion failure in lookup) posted (#2) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/11459 (ctr:Avoid assertion failure in lookup) posted (#3) for review on master by mohammed rafi kc (rkavunga)
COMMIT: http://review.gluster.org/11459 committed in master by Dan Lambright (dlambrig) ------ commit 2e44d1580497eb75f325ad3104249a425ddf592a Author: Mohammed Rafi KC <rkavunga> Date: Tue Jun 30 11:22:31 2015 +0530 ctr:Avoid assertion failure in lookup in ctr_lookup, the loc variable need not be comes with pargfid, though there is a parent for the inode. The same for loc->name also. From this patch, we will generate loc->name from loc->path Change-Id: I24a79554748139504ec09f77930f8208d3805977 BUG: 1236128 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: http://review.gluster.org/11459 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Joseph Fernandes
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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