Bug 1330739

Summary: [RFE] We need more debug info from stack wind and unwind calls
Product: [Community] GlusterFS Reporter: Raghavendra Talur <rtalur>
Component: coreAssignee: Raghavendra Talur <rtalur>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 3.7.11CC: bugs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1330052
: 1332077 (view as bug list) Environment:
Last Closed: 2016-06-28 12:15:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1330052    
Bug Blocks: 1332077    

Description Raghavendra Talur 2016-04-26 20:34:45 UTC
+++ This bug was initially created as a clone of Bug #1330052 +++

Description of problem:
It is possible that some xlators don't print debug/trace logs even when required.
In such cases debugging an existing setup without recompiling becomes very difficult. If libglusterfs/gluster wind/unwind had a debug log builtin then such dependency on every xlator would be reduced.


Version-Release number of selected component (if applicable):
mainline and all previous versions


How reproducible:
Always

--- Additional comment from Vijay Bellur on 2016-04-25 16:45:07 IST ---

REVIEW: http://review.gluster.org/13448 (libglusterfs: Add debug and trace logs for stack trace) posted (#3) for review on master by Raghavendra Talur (rtalur)

Comment 1 Vijay Bellur 2016-04-28 08:09:31 UTC
REVIEW: http://review.gluster.org/14099 (libglusterfs: Add debug and trace logs for stack trace) posted (#1) for review on release-3.7 by Raghavendra Talur (rtalur)

Comment 2 Vijay Bellur 2016-05-02 07:26:52 UTC
REVIEW: http://review.gluster.org/14099 (libglusterfs: Add debug and trace logs for stack trace) posted (#2) for review on release-3.7 by Raghavendra Talur (rtalur)

Comment 3 Vijay Bellur 2016-05-02 10:50:34 UTC
COMMIT: http://review.gluster.org/14099 committed in release-3.7 by Raghavendra Talur (rtalur) 
------
commit f9614a3cb385c1a868443e99f9e50b2252f84b95
Author: Raghavendra Talur <rtalur>
Date:   Mon Feb 15 18:16:04 2016 +0530

    libglusterfs: Add debug and trace logs for stack trace
    
            Backport of http://review.gluster.org/13448
            commit c4d67a8338b42d6485f49999f310cbb9ed5359c5
    
    It has become very difficult to identify the xlator which returned
    negative op_ret. Being able to just change the log level and
    visualize the stack is helpful in such cases.
    
    Change-Id: I6545b4802c1ab4d0d230d5e9e036afb2384882e1
    BUG: 1330739
    Signed-off-by: Raghavendra Talur <rtalur>
    Reviewed-on: http://review.gluster.org/14099
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>

Comment 4 Kaushal 2016-06-28 12:15:37 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.12, please open a new bug report.

glusterfs-3.7.12 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://www.gluster.org/pipermail/gluster-devel/2016-June/049918.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user