7103.html > I see that > your backend sizes are different... Its preferred to keep them uniform. And from this posting: http://gluster.org/pipermail/gluster-users/2011-Marc= h/007104.html > try to keep the backend uniform to avoid any possible issues which may > arise later. 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. -Dan. DISCLAIMER: This e-mail, and any attachments thereto, is intended only for use by the a= ddressee(s)named herein and may contain legally privileged and/or confidential information. If you are = not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or cop= ying of this e-mail and any attachments thereto, is strictly prohibited. If you have received this in error, please= immediately notify me and permanently delete the original and any printout thereof. E-mail transmission cannot be= guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions = in the contents of this message which arise as a result of e-mail transmission. NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Capital Group may, at its discretion, monitor and review the content= of all e-mail communications. http://www.knight.com<http://www.knight.com/> --_000_9AD565C4A8561349B7227B79DDB988737014ACA51AEXCHANGE3glob_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m= icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office= :access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"= uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof= t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co= m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee= t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns= :odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro= soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40"; = xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/"; xmlns:rtc=3D"http://m= icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://= schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share= point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel= /2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd"; xmlns:ois= =3D"http://schemas.microsoft.com/sharepoint/soap/ois/"; xmlns:dir=3D"http://= schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3= .org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint= /dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"; xmlns:xsd=3D"http= ://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha= repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"= xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/"; xmlns:sps=3D"http://= schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001= /XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so= ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile"; xmlns:udc= p2p=3D"http://schemas.microsoft.com/data/udc/parttopart"; xmlns:wf=3D"http:/= /schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche= mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi= crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat= s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf= ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c= om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa= ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web= partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20= 06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200= 6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli= deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal= Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:= st=3D"" xmlns=3D"http://www.w3.org/TR/REC-html40";><head><meta http-equi= v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen= erator content=3D"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=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite lang=3DEN-US= link=3Dblue vlink=3Dpurple><!--ppd1000033--><div class=3DWordSection1><p c= lass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","san= s-serif";color:#1F497D'>Hi Dan.<o:p></o:p></span></p><p class=3DMsoNormal><= span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F= 497D'><o:p> </o:p></span></p><p class=3DMsoNormal><span style=3D'font-= size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I believe tha= t you would have to run this command:<o:p></o:p></span></p><p class=3DMsoNo= rmal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";col= or:#1F497D'><o:p> </o:p></span></p><p class=3DMsoNormal><span style=3D= 'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>gluster= volume rebalance <volname> start<o:p></o:p></span></p><p class=3DMso= Normal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c= olor:#1F497D'><o:p> </o:p></span></p><p class=3DMsoNormal><span style= =3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>at w= hich 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 actua= l space available and try to make intelligent decisions on where to place f= iles.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11= .0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></s= pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"C= alibri","sans-serif";color:#1F497D'>Please check with the devs before imple= menting my suggestion, however – don’t want to cause any harm s= ince I’m unsure.<o:p></o:p></span></p><p class=3DMsoNormal><span styl= e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:= p> </o:p></span></p><div><p class=3DMsoNormal><span style=3D'font-size= :8.0pt;font-family:"Arial","sans-serif";color:#003D79'>James Burnash, Unix = Engineering<o:p></o:p></span></p></div><p class=3DMsoNormal><span style=3D'= font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nb= sp;</o:p></span></p><div><div style=3D'border:none;border-top:solid #B5C4DF= 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'fo= nt-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</s= pan></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";c= olor:windowtext'> gluster-users-bounces at gluster.org [mailto:gluster-users-b= ounces at gluster.org] <b>On Behalf Of </b>Dan Bretherton<br><b>Sent:</b> Sund= ay, May 01, 2011 9:01 AM<br><b>To:</b> gluster-users<br><b>Subject:</b> [SP= AM?] Non-uniform backend brick sizes<br><b>Importance:</b> = Low<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p> </o:p>= </p><p class=3DMsoNormal>Hello All-<br>After posting to a previous thread a= bout this issue (<a href=3D"http://gluster.org/pipermail/gluster-users/2011= -April/007157.html">http://gluster.org/pipermail/gluster-users/2011-April/0= 07157.html</a>) I decided to start a new thread, mainly because I think I h= ave 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.&= nbsp; 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" err= ors even though df reported several hundred GB free in the volume. Th= e problem turned out to be caused by over-writing pre-existing files that w= ere stored on one or more full bricks. Deleting the old files before = creating them again cured the problem, because the new files were then crea= ted on larger bricks. Is this a known problem when using distributed = or distributed/replicated volumes with non uniform backend sizes, and is th= ere any way to avoid it?<br><br>Lifting some comments and questions from th= e other thread...<br><br>From this posting: <a href=3D"http://gluster.org/p= ipermail/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 tha= t<o:p></o:p></pre><pre>> your backend sizes are different... Its preferr= ed to keep them uniform.<span style=3D'font-size:12.0pt'><o:p></o:p><= /span></pre><p class=3DMsoNormal>And from this posting: <a href=3D"http://g= luster.org/pipermail/gluster-users/2011-March/007104.html">http://gluster.o= rg/pipermail/gluster-users/2011-March/007104.html</a><o:p></o:p></p><pre>&g= t; 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=3DMsoNormal = style=3D'margin-bottom:12.0pt'>Please could someone comment on the "po= ssible issues that might arise" with with a setup involving non-unifor= m backend brick sizes. All comments and suggestions would be much app= reciated.<br><br>-Dan.<span style=3D'font-size:13.5pt'><br><br></span><o:p>= </o:p></p></div><br /><br /> <P><FONT color=3Dnavy><FONT size=3D1>DISCLAIMER:<BR>This e-mail, and any at= tachments=20 thereto, is intended only for use by the addressee(s)named herein and<BR>ma= y=20 contain legally privileged and/or confidential information. If you are not = the=20 intended recipient of this<BR>e-mail, you are hereby notified that any=20 dissemination, distribution or copying of this e-mail and any=20 attachments</FONT><FONT color=3Dnavy><BR></FONT><FONT size=3D1>thereto, is = strictly=20 prohibited. If you have received this in error, please immediately notify m= e and=20 permanently<BR>delete the original and any printout thereof.</FONT></FONT><= FONT=20 size=3D1> </FONT><FONT color=3Dnavy size=3D1>E-mail transmission cannot be = guaranteed=20 to be secure or error-free.<BR>The sender therefore does not accept liabili= ty=20 for any errors or omissions in the contents of this message which<BR>arise = as a=20 result of e-mail transmission.<BR>NOTICE REGARDING PRIVACY AND=20 CONFIDENTIALITY<BR>Knight Capital Group may, at its discretion, monitor and= =20 review the content of all e-mail communications.</FONT></P> <P><A href=3D"http://www.knight.com/";><FONT color=3Dnavy=20 size=3D1>http://www.knight.com</FONT></A><BR></P> &n= bsp; =20 </body></html>= --_000_9AD565C4A8561349B7227B79DDB988737014ACA51AEXCHANGE3glob_--
