Description of problem: Each every time when a gluster command is executed directly, the following error is being logged in cli logs. [2015-07-16 06:21:22.746577] E [mem-pool.c:417:mem_get0] (-->/usr/local/lib/libglusterfs.so.0(+0x7e262) [0x7fdbc0b1f262] -->/usr/local/lib/libglusterfs.so.0(_gf_msg+0x804) [0x7fdbc0ac7844] -->/usr/local/lib/libglusterfs.so.0(mem_get0+0x78) [0x7fdbc0af5b48] ) 0-mem-pool: invalid argument [Invalid argument] Version-Release number of selected component (if applicable): master How reproducible: Always Steps to Reproduce: 1. Build glusterfs from master and start glusterd service 2. Execute any gluster command and check cli logs for the above mentioned error. Actual results: Error logs are seen. Expected results: No errors are seen. Additional info:
REVIEW: http://review.gluster.org/11691 (cli: Create missing logbuf_pool) posted (#1) for review on master by Anoop C S (achiraya)
COMMIT: http://review.gluster.org/11691 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 4cdeee511ef8bab977cbb31bc2e8f005fe340ef1 Author: Anoop C S <anoopcs> Date: Thu Jul 16 13:56:51 2015 +0530 cli: Create missing logbuf_pool Since logbuf_pool was not created via glusterfs_ctx_defaults_init(), the following error was present in cli logs repeateadly for each and every execution of a gluster command. E [mem-pool.c:417:mem_get0] (-->/usr/local/lib/libglusterfs.so.0(+0x7e262) [0x7fdbc0b1f262] -->/usr/local/lib/libglusterfs.so.0(_gf_msg+0x804) [0x7fdbc0ac7844] -->/usr/local/lib/libglusterfs.so.0(mem_get0+0x78) [0x7fdbc0af5b48] ) 0-mem-pool: invalid argument [Invalid argument] This change creates ctx->logbuf_pool via glusterfs_ctx_defaults_init() in cli.c so that the above error is no longer logged in cli logs. Change-Id: I3fcd9cfefa06ddd52e1989b039ff5637372c3235 BUG: 1243753 Signed-off-by: Anoop C S <anoopcs> Reviewed-on: http://review.gluster.org/11691 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Krishnan Parthasarathi <kparthas>
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.