<div><br><div class="gmail_quote"><div>On Fri, 31 Mar 2017 at 18:15, Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Mar 31, 2017 at 02:34:04PM +0530, Sanoj Unnikrishnan wrote:<br class="gmail_msg">
> +Mohit<br class="gmail_msg">
> Mohit had written a similar script to RCA an issue couple of months back.<br class="gmail_msg">
><br class="gmail_msg">
> It would help if we placed the scripts, tapsets in the source tree itself<br class="gmail_msg">
> (maybe in a directory under glusterfs/extras/).<br class="gmail_msg">
> We could also have the tapset packaged into debuginfo packages and deployed<br class="gmail_msg">
> under /usr/share/systemtap/ path upon installation.<br class="gmail_msg">
<br class="gmail_msg">
Yes, or we can place them in their own repository. I have a<br class="gmail_msg">
gluster-debug repository where I plan to put tools I use for debugging.<br class="gmail_msg">
This repository may well live at the Gluster organization on GitHub too.<br class="gmail_msg">
<br class="gmail_msg">
<a href="https://github.com/nixpanic/gluster-debug" rel="noreferrer" class="gmail_msg" target="_blank">https://github.com/nixpanic/gluster-debug</a><br class="gmail_msg">
<br class="gmail_msg">
Many of the tools we use for debugging should not be version specific,<br class="gmail_msg">
so having them in the glusterfs repository might be a little awkward?<br class="gmail_msg">
<br class="gmail_msg">
What are the opinions of others?</blockquote><div><br></div><div>My personal preference would be to host it under one central repo instead of individual github accounts. Versioning and such other issues can be tackled having good documentation around these tools.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg">
<br class="gmail_msg">
Thanks,<br class="gmail_msg">
Niels<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
> Regards,<br class="gmail_msg">
> Sanoj<br class="gmail_msg">
><br class="gmail_msg">
> On Fri, Mar 31, 2017 at 12:44 PM, Sonal Arora <<a href="mailto:sarora@redhat.com" class="gmail_msg" target="_blank">sarora@redhat.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> > Hi,<br class="gmail_msg">
> ><br class="gmail_msg">
> > I am working on finding ways to indentify ref leaks in glusterfs.<br class="gmail_msg">
> ><br class="gmail_msg">
> > Description of Issue : <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1417539" rel="noreferrer" class="gmail_msg" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1417539</a><br class="gmail_msg">
> ><br class="gmail_msg">
> > Goal : To make script which could detect all kind of ref leaks.<br class="gmail_msg">
> ><br class="gmail_msg">
> > Script : <a href="https://github.com/SonaArora/Tracing-userspace-app/blob/" rel="noreferrer" class="gmail_msg" target="_blank">https://github.com/SonaArora/Tracing-userspace-app/blob/</a><br class="gmail_msg">
> > master/ref-leak/try8-modified<br class="gmail_msg">
> > The above script is a POC program to depict the idea of how to identify<br class="gmail_msg">
> > leaks. Script is probing dict_ref() and dict_unref() and keeping a track of<br class="gmail_msg">
> > the pointers, back traces which are referenced/dereferenced by above<br class="gmail_msg">
> > functions. If the count of refs is unequal to unrefs for each pointer,it<br class="gmail_msg">
> > will print all the traces corresponding to the leaked pointer.<br class="gmail_msg">
> > Output : <a href="https://github.com/SonaArora/Tracing-userspace-" rel="noreferrer" class="gmail_msg" target="_blank">https://github.com/SonaArora/Tracing-userspace-</a><br class="gmail_msg">
> > app/blob/master/ref-leak/output-refleak<br class="gmail_msg">
> > I am working on post processing the output - to filter only the leaked<br class="gmail_msg">
> > traces and to write the output after every few hours into a file.<br class="gmail_msg">
> > The script can be extended to all objects being referenced (like<br class="gmail_msg">
> > inodes/fds).<br class="gmail_msg">
> ><br class="gmail_msg">
> > End Goal : Future goal is to make it more versatile, dynamic and light<br class="gmail_msg">
> > weight so that it can be even utilized on production environments without<br class="gmail_msg">
> > utilizing much of the system resources.<br class="gmail_msg">
> ><br class="gmail_msg">
> > Request your comments and suggestions.<br class="gmail_msg">
> ><br class="gmail_msg">
> > Best<br class="gmail_msg">
> > -Sonal<br class="gmail_msg">
> ><br class="gmail_msg">
> ><br class="gmail_msg">
> ><br class="gmail_msg">
> > _______________________________________________<br class="gmail_msg">
> > Gluster-devel mailing list<br class="gmail_msg">
> > <a href="mailto:Gluster-devel@gluster.org" class="gmail_msg" target="_blank">Gluster-devel@gluster.org</a><br class="gmail_msg">
> > <a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-devel</a><br class="gmail_msg">
> ><br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
Gluster-devel mailing list<br class="gmail_msg">
<a href="mailto:Gluster-devel@gluster.org" class="gmail_msg" target="_blank">Gluster-devel@gluster.org</a><br class="gmail_msg">
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-devel</a></blockquote></div></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature">- Atin (atinm)</div>