<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I can't view that bug, I get "<span style="font-family: 'DejaVu Sans', 'Liberation Sans', sans-serif; font-size: x-large; background-color: rgb(255, 0, 0); ">You are not authorized to access bug #874554"</span><br><div><div><br></div><div>What version of gluster will have the fix? Will it be in 3.3.2, and if so when will that be released?</div><div><br></div><div>-Tom</div><div><br></div><div>On Apr 16, 2013, at 1:02 AM, Varun Shastry <<a href="mailto:vshastry@redhat.com">vshastry@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Thomos,<br><br>It was a bug <a href="https://bugzilla.redhat.com/show_bug.cgi?id=874554">https://bugzilla.redhat.com/show_bug.cgi?id=874554</a> and its fixed now.<br><br>-Varun Shastry<br><br>On Tuesday 16 April 2013 12:18 AM, Thomas Wakefield wrote:<br><blockquote type="cite">Was there ever a solution for setting min-free-disk? I have a cluster of about 30 bricks, some are 8TB and new bricks are 50TB. I should be able to set gluster to leave 500GB free on each brick. But one of the 8TB bricks keeps filling up with new data.<br><br>This is my current setting:<br>cluster.min-free-disk: 500GB<br><br><br>Thoughts?<br><br>Running 3.3.1.<br><br>-Tom<br><br><br>On Aug 26, 2012, at 2:15 AM, James Kahn <<a href="mailto:jkahn@idea11.com.au">jkahn@idea11.com.au</a>> wrote:<br><br><blockquote type="cite">Further to my last email, I've been trying to find out why GlusterFS is<br>favouring one brick over another. In pretty much all of my tests gluster<br>is favouring the MOST full brick to write to. This is not a good thing<br>when the most full brick has less than 200GB free and I need to write a<br>huge file to it.<br><br>I've set cluster.min-free-disk on the volume, and it doesn't seem to have<br>an effect. At all. I've tried setting it to 25%, and 400GB. When I run<br>tests from an NFS client, they get written to the most full brick. There<br>is less than 10% free on that brick so it should be ignore with the<br>defaults anyway.<br><br>Any ideas?<br><br>JK<br><br><br><br><br><br>_______________________________________________<br>Gluster-users mailing list<br><a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>http://gluster.org/cgi-bin/mailman/listinfo/gluster-users<br></blockquote>_______________________________________________<br>Gluster-users mailing list<br><a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>http://supercolony.gluster.org/mailman/listinfo/gluster-users<br></blockquote><br></blockquote></div><br></body></html>