Red Hat Bugzilla – Bug 1231792
libglusterfs: Porting log messages to new framework and allocating segments
Last modified: 2016-09-17 10:37:27 EDT
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
libglusterfs: Introducing new logging message https://code.engineering.redhat.com/gerrit/51144/ Backport of http://review.gluster.org/9898 in master common-utils/libglusterfs : Porting to a new logging framework https://code.engineering.redhat.com/gerrit/51146/ Backport of http://review.gluster.org/10824 in master fd,inode/libglusterfs : porting to a new logging framework https://code.engineering.redhat.com/gerrit/51214/ Backport of http://review.gluster.org/10825/ in master
call-stub,circ-buff,client_t,compat,dict/libglusterfs : Porting to a new logging framework https://code.engineering.redhat.com/gerrit/#/c/51686/ Backport of http://review.gluster.org/10828 graph/libglusterfs : porting to a new logging framework https://code.engineering.redhat.com/gerrit/#/c/51692/ Backport of http://review.gluster.org/10822 defaults,globals,iobuf,latency,logging,options,xlator/libglusterfs : porting to a new logging framework https://code.engineering.redhat.com/gerrit/#/c/51693/ Backport of http://review.gluster.org/10826 event,parse-utils,quota-common-utils,rbthash/libglusterfs : Porting to new logging framework https://code.engineering.redhat.com/gerrit/#/c/51695/ Backport of http://review.gluster.org/10823 common-utils/libglusterfs : removing strerror to avoid duplicate printing of error message https://code.engineering.redhat.com/gerrit/#/c/51749/ Backport of http://review.gluster.org/11400 mem-pool,stack,store,syncop,timer/libglusterfs : Porting to a new logging framework https://code.engineering.redhat.com/gerrit/#/c/51751/ Backport of http://review.gluster.org/10827
All the patches merged
Tested with RHGS-3.1 ( glusterfs-3.7.1-8.el6rhs ). There are few occurrences of gf_log and gf_log_calling function for which a bug - https://bugzilla.redhat.com/show_bug.cgi?id=1242211 - is filed Marking this bug as VERIFIED
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/RHSA-2015-1495.html