glusterfs.git/extras/devel-tools, branch v7.8

extras/devel-tools: script to strace processes

2018-09-19T03:30:20+00:00

Script to strace processes at high priority.
Script should be run at high priority, like nice value of -19, to help
get a trace of a run-away process consuming high CPU.

eg.
$ nice -n -19 ./strace-brick.sh glusterfsd 50

will strace glusterfsd processes for 60 seconds which are consuming a
minimum of 50% CPU.

Change-Id: I6374054c7342b19122a3588d982388199f955930
BUG: 1427397
Signed-off-by: Milind Changire

extras/devel-tools: script to resolve backtraces

2018-09-18T09:11:30+00:00

print-backtrace.sh
script to resolve backtraces

Change-Id: I24688ae5160cc706d9f4794521d17290bef6765b
BUG: 1486532
Signed-off-by: Milind Changire

extras/devel-tools: Fix print-backtrace script

2017-11-26T23:05:14+00:00

Problem:
If cpio version is less 2.11 then cpio command failing with
unrecognised option --directory.

Solution:
Check the cpio version and run rpm2cpio/cpio with or without
-D or --directory option.

Fixes : #359
Change-Id: Ibd440207231807dab1b58291ab661857094f1a4a
BUG: 1510874
Signed-off-by: Prashant D

extras/devel-tools: script to resolve bt addresses

2017-03-08T03:52:16+00:00

Problem:
STACK_WINDs in a gluster backtrace dumped in a log file are
undecipherable with only the hex addresses of the location
leaving us without a clue.

Solution:
This utility uses the undeciphered lines in the backtrace and the
associated debuginfo rpm to generate the function name and the file and
line number associated with the stack frame.

Passing "none" as the debuginfo rpm name will make the script assume
that you want to resolve against a source install and not a debuginfo
rpm.

You would need to copy the unresolved lines from the backtrace into a
file and pass the name of this file to the utility as the input file.

Change-Id: I4d8bc1ae205af37688d03298de49654018bdba9d
BUG: 1426891
Signed-off-by: Milind Changire 
Reviewed-on: https://review.gluster.org/16763
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Vijay Bellur

extra/devel-vagrant: accept gluster src location from user

2016-05-18T17:10:14+00:00

Currently gluster source location is hard-coded in vagrantfile.

Made the source location user configurable and also fixed minor issue
with peer probe with single node.

Change-Id: I7057a97d7372477ddbf01fbc8db949923dfd86e8
BUG: 1336354
Signed-off-by: Rajesh Joseph 
Reviewed-on: http://review.gluster.org/14354
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Jeff Darcy

devel-tools: vagrant setup for creating devel VMs

2016-04-26T12:28:01+00:00

Created vagrant setup for Gluster developers. The Vagrantfile
is modifed from the work done by Chris (cblum@redhat.com).
Ansible structure is taken from test vagrant infra initially
posted by rtalur.

This vagrant setup can create one or more VM (using libvirt),
create thinly provisioned LVs, format them with XFS and mount them.
It will also compile the source from host machine (/work/source) and
install gluster. It will also do peer probe.

Change-Id: Ie984f661bb5dc9cfc4059643389d3c80b2cae21d
BUG: 1327976
Signed-off-by: Rajesh Joseph 
Reviewed-on: http://review.gluster.org/13734
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Raghavendra Talur 
Tested-by: Raghavendra Talur

extras/devel-tool: Added gdb_macros for debugging

2016-02-02T07:43:46+00:00

provided following functions in the script
1) print dictionary (dict_t) items
2) print list members (only address)

Change-Id: I5befb2dcdbf258ab3001ff25212a5862b9cc5321
Signed-off-by: Rajesh Joseph 
Reviewed-on: http://review.gluster.org/13289
Smoke: Gluster Build System 
Reviewed-by: Raghavendra Talur 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System