[Bugs] [Bug 1252695] New: posix : pending - porting log messages to a new framework

bugzilla at redhat.com bugzilla at redhat.com
Wed Aug 12 06:12:53 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1252695

            Bug ID: 1252695
           Summary: posix : pending - porting log messages to a new
                    framework
           Product: GlusterFS
           Version: mainline
         Component: posix
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: hgowtham at redhat.com
                CC: annair at redhat.com, bugs at gluster.org,
                    gluster-bugs at redhat.com, rhs-bugs at redhat.com,
                    sasundar at redhat.com
        Depends On: 1242021
            Blocks: 1241957



+++ This bug was initially created as a clone of Bug #1242021 +++

Description of problem:
------------------------
There are occurrences of gf_log and gf_log_callingfn under posix.
These instances should be ported to the corresponding gf_msg functions

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHGS 3.1 ( glusterfs-3.7.1-8el6rhs )

Info
-----
gf_log instances
================
[satheesaran at dhcppc1 posix]$ grep -r 'gf_log ' * -A1
src/posix.c: gf_log (this->name, GF_LOG_ERROR,
src/posix.c- "fsetxattr (fstat) failed on fd=%p: %s",

gf_log_callingfn instances
===========================
[satheesaran at dhcppc1 posix]$ grep -r 'gf_log_callingfn ' * -A1
src/posix-helpers.c: callingfn (this->name, GF_LOG_DEBUG, "failed to get
gfid");

src/posix.c: gf_log_callingfn (this->name, GF_LOG_ERROR, "Invalid Args: "
src/posix.c-             "fd: %p inode: %p gfid:%s", fd, inode?inode:0,


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1241957
[Bug 1241957] [ TRACKER ] : Tracker for porting pending log messages
porting to new framework
https://bugzilla.redhat.com/show_bug.cgi?id=1242021
[Bug 1242021] posix : pending - porting log messages to a new framework
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list