+++ This bug was initially created as a clone of Bug #1174087 +++ Description of problem: Quite a few log messages in marker translator are incorrect. This needs to be fixed. --- Additional comment from Anand Avati on 2014-12-15 00:30:20 EST --- REVIEW: http://review.gluster.org/8168 (features/marker: log message clean up) posted (#4) for review on master by Vijay Bellur (vbellur) --- Additional comment from Anand Avati on 2014-12-26 02:32:17 EST --- COMMIT: http://review.gluster.org/8168 committed in master by Raghavendra G (rgowdapp) ------ commit 79a5b2b991037cc1db5c71f7aa2a32ce712a22e9 Author: Vijay Bellur <vbellur> Date: Mon Jun 23 22:59:14 2014 +0530 features/marker: log message clean up 1. Changed log messages to be more appropriate. 2. Changed loglevel of failures in fop_cbks to be recorded as TRACE. Logging of failures at higher loglevels is unessential in non-endpoint translators. 3. Removed a log message related to memory allocation failure. BUG: 1174087 Change-Id: I63c560c3bbd12706357fb3f696378c1a1e1efb44 Signed-off-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/8168 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaleb KEITHLEY <kkeithle> Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Raghavendra G <rgowdapp>
REVIEW: http://review.gluster.org/9525 (features/marker: log message clean up) posted (#1) for review on release-3.6 by Vijay Bellur (vbellur)
COMMIT: http://review.gluster.org/9525 committed in release-3.6 by Raghavendra Bhat (raghavendra) ------ commit 2d45a5557f9e6a797e39d3383d851e8812fa91c0 Author: Vijay Bellur <vbellur> Date: Mon Jun 23 22:59:14 2014 +0530 features/marker: log message clean up 1. Changed log messages to be more appropriate. 2. Changed loglevel of failures in fop_cbks to be recorded as TRACE. Logging of failures at higher loglevels is unessential in non-endpoint translators. 3. Removed a log message related to memory allocation failure. BUG: 1188066 Change-Id: I63c560c3bbd12706357fb3f696378c1a1e1efb44 Signed-off-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/8168 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaleb KEITHLEY <kkeithle> Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Raghavendra G <rgowdapp> Reviewed-on: http://review.gluster.org/9525 Reviewed-by: Raghavendra Bhat <raghavendra>
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