Bug 845114 - possible to miss information of missing frames during backtrace and statedump
Summary: possible to miss information of missing frames during backtrace and statedump
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: logging
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-01 20:05 UTC by Amar Tumballi
Modified: 2013-12-19 00:08 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:32:31 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Amar Tumballi 2012-08-01 20:05:31 UTC 
Description of problem:
there is a possibility of missing the frame information if the frames are created outside the 'fop' context in statedump and backtrace log. 

have a patch ready to solve this... more detail with the patch
Comment 1 Amar Tumballi 2012-08-02 03:11:23 UTC 
http://review.gluster.com/3768 - print all missing frames has been merged to upstream.
Note You need to log in before you can comment on or make changes to this bug.