Description of problem: ----------------------- Observed error messages in cli.log log message file. [2015-07-15 17:18:20.279219] E [mem-pool.c:417:mem_get0] (-->/lib64/libglusterfs.so.0(+0x873d2) [0x7f92a664f3d2] -->/lib64/libglusterfs.so.0(_gf_msg+0x79a) [0x7f92a65ef45a] -->/lib64/libglusterfs.so.0(mem_get0+0x81) [0x7f92a66216f1] ) 0-mem-pool: invalid argument [Invalid argument] Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHGS 3.1 Nightly build ( glusterfs-3.7.1-9.el6rhs ) How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Initiate any gluster command 2. Look for error messages in cli.log Actual results: --------------- There were error messages in cli.log Expected results: ----------------- There shouldn't be any error messages
There is no functional impact, just that these error messages are seen in cli.log But I think that this bug should be raised as a known_issue
This bug has been already fixed in upstream by http://review.gluster.org/11691 and is also available in 3.1.2 as part of rebasing. Moving the status to ON_QA. Also providing devel_ack for this.
Tested with glusterfs-3.7.5-11.el7rhgs cli.log no longer has error messages
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0193.html