<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi James, thanks for your suggestions. I have used the rebalance
command several times after adding new bricks, and I am pretty sure
that it equalizes the amount of data stored on each brick rather
than the amount of free space. It would be useful to have an option
to equalize free space instead - that would certainly solve the
problem of non-uniform brick sizes.<br>
<br>
There used to be a server vol file option "min-free-disk", to leave
space on bricks for files to grow. That would solve my problem as
well. Do you know if this is available in 3.1.x or 3.2, or if there
is a CLI command for setting it?<br>
<br>
-Dan.<br>
<br>
On 02/05/11 13:11, Burnash, James wrote:
<blockquote
cite="mid:9AD565C4A8561349B7227B79DDB988737014ACA51A@EXCHANGE3.global.knight.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--><!--ppd1000033-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Hi Dan.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">I believe that you would have to run this
command:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">gluster volume rebalance <volname> start<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">at which point, Gluster will try to balance the
files amongst the storage nodes. Whether or not it will
accommodate non-uniform bricks I don’t know for sure (since
mine are uniform), but I believe that it will look at actual
space available and try to make intelligent decisions on
where to place files.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Please check with the devs before implementing my
suggestion, however – don’t want to cause any harm since I’m
unsure.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size: 8pt; font-family:
"Arial","sans-serif"; color: rgb(0,
61, 121);">James Burnash, Unix Engineering<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border-right: medium none; border-width: 1pt
medium medium; border-style: solid none none; border-color:
rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color;
padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif"; color:
windowtext;">From:</span></b><span style="font-size:
10pt; font-family:
"Tahoma","sans-serif"; color:
windowtext;"> <a class="moz-txt-link-abbreviated" href="mailto:gluster-users-bounces@gluster.org">gluster-users-bounces@gluster.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gluster-users-bounces@gluster.org">mailto:gluster-users-bounces@gluster.org</a>] <b>On Behalf
Of </b>Dan Bretherton<br>
<b>Sent:</b> Sunday, May 01, 2011 9:01 AM<br>
<b>To:</b> gluster-users<br>
<b>Subject:</b> [SPAM?] [Gluster-users] Non-uniform
backend brick sizes<br>
<b>Importance:</b> Low<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello All-<br>
After posting to a previous thread about this issue (<a
moz-do-not-send="true"
href="http://gluster.org/pipermail/gluster-users/2011-April/007157.html">http://gluster.org/pipermail/gluster-users/2011-April/007157.html</a>)
I decided to start a new thread, mainly because I think I have
found a problem relating to this setup. Our servers vary in
size quite a lot, so some of the bricks in one particular
volume are 100% full. This has not caused us any problems
until now, because new files are always created on larger
bricks where there is still space. However, yesterday a user
complained that he was getting "device full" errors even
though df reported several hundred GB free in the volume. The
problem turned out to be caused by over-writing pre-existing
files that were stored on one or more full bricks. Deleting
the old files before creating them again cured the problem,
because the new files were then created on larger bricks. Is
this a known problem when using distributed or
distributed/replicated volumes with non uniform backend sizes,
and is there any way to avoid it?<br>
<br>
Lifting some comments and questions from the other thread...<br>
<br>
From this posting: <a moz-do-not-send="true"
href="http://gluster.org/pipermail/gluster-users/2011-March/007103.html">http://gluster.org/pipermail/gluster-users/2011-March/007103.html</a><o:p></o:p></p>
<pre>> I see that<o:p></o:p></pre>
<pre>> your backend sizes are different... Its preferred to keep them uniform.<span style="font-size: 12pt;"><o:p></o:p></span></pre>
<p class="MsoNormal">And from this posting: <a
moz-do-not-send="true"
href="http://gluster.org/pipermail/gluster-users/2011-March/007104.html">http://gluster.org/pipermail/gluster-users/2011-March/007104.html</a><o:p></o:p></p>
<pre>> try to keep the backend uniform to avoid any possible issues which may<o:p></o:p></pre>
<pre>> arise later.<o:p></o:p></pre>
<p class="MsoNormal" style="margin-bottom: 12pt;">Please could
someone comment on the "possible issues that might arise" with
with a setup involving non-uniform backend brick sizes. All
comments and suggestions would be much appreciated.<br>
<br>
-Dan.<span style="font-size: 13.5pt;"><br>
<br>
</span><o:p></o:p></p>
</div>
<br>
<br>
<p><font color="navy"><font size="1">DISCLAIMER:<br>
This e-mail, and any attachments thereto, is intended only
for use by the addressee(s)named herein and<br>
may contain legally privileged and/or confidential
information. If you are not the intended recipient of this<br>
e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail and any attachments</font><font
color="navy"><br>
</font><font size="1">thereto, is strictly prohibited. If you
have received this in error, please immediately notify me
and permanently<br>
delete the original and any printout thereof.</font></font><font
size="1"> </font><font color="navy" size="1">E-mail
transmission cannot be guaranteed to be secure or error-free.<br>
The sender therefore does not accept liability for any errors
or omissions in the contents of this message which<br>
arise as a result of e-mail transmission.<br>
NOTICE REGARDING PRIVACY AND CONFIDENTIALITY<br>
Knight Capital Group may, at its discretion, monitor and
review the content of all e-mail communications.</font></p>
<p><a moz-do-not-send="true" href="http://www.knight.com/"><font
color="navy" size="1">http://www.knight.com</font></a><br>
</p>
</blockquote>
</body>
</html>