Description of problem: The following error log related to CTR translator is being generated in brick logs at each volume start. [ctr-helper.c:256:extract_ctr_options] 0-gfdbdatastore: CTR Xlator is disabled. Version-Release number of selected component (if applicable): mainline How reproducible: Always Steps to Reproduce: 1. Create and start simple distributed volume. 2. Check the brick logs for the above mentioned message. Actual results: Error log entry is seen. Expected results: Error log shouldn't be present in brick logs. Additional info:
REVIEW: http://review.gluster.org/11592 (features/ctr: Reduce the log-level for ctr-disabled message) posted (#1) for review on master by Anoop C S (achiraya)
COMMIT: http://review.gluster.org/11592 committed in master by Dan Lambright (dlambrig) ------ commit b6a7a44079c724cbf6fb24c7ac83892f551dc5f6 Author: Anoop C S <anoopcs> Date: Thu Jul 9 11:06:01 2015 +0530 features/ctr: Reduce the log-level for ctr-disabled message Since by default CTR translator is disabled, the following log message is being displayed in brick logs. [ctr-helper.c:256:extract_ctr_options] 0-gfdbdatastore: CTR Xlator is disabled. Therefore this change is to reduce the log-level to INFO. Change-Id: I3b82d6b0dc0445286f91490fb497167a36914a2b BUG: 1241379 Signed-off-by: Anoop C S <anoopcs> Reviewed-on: http://review.gluster.org/11592 Reviewed-by: Joseph Fernandes Tested-by: Joseph Fernandes Tested-by: NetBSD Build System <jenkins.org>
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.