REVIEW: http://review.gluster.org/12391 (cluster/tier remove suprious log messages on valid failed migration) posted (#1) for review on master by Dan Lambright (dlambrig)
COMMIT: http://review.gluster.org/12391 committed in master by Dan Lambright (dlambrig) ------ commit 116430b5e44457bba515a83be26b4b2256c75c38 Author: Dan Lambright <dlambrig> Date: Mon Oct 19 09:04:07 2015 -0400 cluster/tier remove suprious log messages on valid failed migration On a write to a replica volume, we record in all brick's databases an entry. When the tier daemon runs, it will only move the file if it is the true owner of the file as defined by the XATTR_NODE_UUID_KEY. Change-Id: Ib82717f87a3f94f3d0d9f969773de9e88d6aaf22 BUG: 1273043 Signed-off-by: Dan Lambright <dlambrig> Reviewed-on: http://review.gluster.org/12391 Reviewed-by: Joseph Fernandes Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/13114 (cluster/tier: Additional details in error messages) posted (#1) for review on master by N Balachandran (nbalacha)
http://review.gluster.org/13114 adds additional information when available in log messages to help with debugging
REVIEW: http://review.gluster.org/13114 (cluster/tier: Additional details in error messages) posted (#2) for review on master by N Balachandran (nbalacha)
COMMIT: http://review.gluster.org/13114 committed in master by Dan Lambright (dlambrig) ------ commit 50d14b2aec654eaf95a467bc12a8c6fd396cfb0a Author: N Balachandran <nbalacha> Date: Wed Dec 30 14:55:48 2015 +0530 cluster/tier: Additional details in error messages Added file path/gfid when available to the tier log messages to make debugging easier. Change-Id: I22dda329367df2b846dcf254594312c997b66083 BUG: 1273043 Signed-off-by: N Balachandran <nbalacha> Reviewed-on: http://review.gluster.org/13114 Reviewed-by: mohammed rafi kc <rkavunga> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Dan Lambright <dlambrig> Tested-by: Dan Lambright <dlambrig>
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