Red Hat Bugzilla – Bug 844688
improvements in statedumps
Last modified: 2013-09-23 18:32:56 EDT
Description of problem:
Statedumps of the glusterfs processes need to be improved, such as a start and end marker should be added in the statedump files which indicates beginning and end of the statedump information. Apart from that in statedumps gf_log should not be used and instead of pthread_mutex_lock, pthread_mutex_trylock should be used to avoid deadlocks.
Also the names of the statedump files should be changed by appending the timestamp the filename. Otherwise of statedump is issued on the same glusterfs process again, then the old statedump information is lost.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Gluster dump generated by sosreport now has the start and end markers. And the generated files are named by appending the timestamps to the file.
After extracting the sosreport archive, the files can be found under: sos_commands/gluster/glusterfs-statedumps
The generated dump file look like: exports-840811.14584.dump.1357565301 exports-dist.27134.dump.1357565301 glusterdump.19754.dump.1357565301
And the header and footer contains the strings:
DUMP-START-TIME: 2013-01-07 13:28:21.862228 and DUMP-END-TIME: 2013-01-07 13:28:21.879735 respectively which will help us determine if the dump contains all the data from the process.
CHANGE: http://review.gluster.org/4087 (libglusterfs/core: dump frame and callstack creation times in statedump) merged in master by Anand Avati (email@example.com)
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.