<pre class="bz_comment_text" id="comment_text_1">Hi Gordon,<br><br>There was a patch submitted by gowda and accepted regarding a memory leak in<br>logging.<br><a href="http://patches.gluster.com/patch/679/"></a><br>The commit id is 8d74fe9ba6c3c2f68f71cacd56fad9328b8b0090<br>
<br>Can this fix the leak observed above?<br><br>regards,<br>Raghavendra</pre><br><br><div class="gmail_quote">On Thu, Jul 9, 2009 at 1:32 AM, Gordan Bobic <span dir="ltr"><<a href="mailto:gordan@bobich.net">gordan@bobich.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Anand Avati wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have just put it back as it was (mounted with<br>
-o direct-io-mode=off,log-level=NONE,log-file=/dev/null<br>
and sure enough the leak disappeared. The CPU usage is also down to a much<br>
more reasonable 25-30%.<br>
<br>
Should I bother with a bugzilla report, or is this already a known issue in<br>
2.0.2?<br>
</blockquote>
<br>
We have not faced any leaks associated with direct-io-mode or logs.<br>
Please do file a bug report with the steps to reproduce it.<br>
</blockquote>
<br></div>
Filed bug 122.<br><font color="#888888">
<br>
Gordan</font><div><div></div><div class="h5"><br>
<br>
<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br>
<a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Raghavendra G<br><br>