<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1170634489;
mso-list-type:hybrid;
mso-list-template-ids:610422992 1267752732 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:24.75pt;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thank you to everyone who helped me with the Fedora 10 rpmbuild
issue. The “--without modglfs” worked like a charm.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I would like to do a sanity check on a GlusterFS design I
was planning to implement. I have a situation where I have many machines, each
with different amounts of disk storage available under a /scratch mountpoint.
As a first step, I would like to use the “distribute” translator to
distribute files among these machines and present a unified view of the files.
Second, I would like to add redundancy, so that each file is stored on at least
two machines and can easily be recovered if a node crashes.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>My idea was to create two directories on each machine called
“/scratch/.glusterfs_storage_primary” and “/scratch/.glusterfs_storage_secondary”
and expose them as bricks. Then I would then have two instances of the
distribute translator, one which would aggregate all the “.glusterfs_storage_primary”
bricks, and the other which would aggregate all the “.glusterfs_storage_secondary”
bricks. Then, on top of that, I would use the replicate translator with self-healing
to replicate files across these two aggregates.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>My questions:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoListParagraph style='margin-left:24.75pt;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>1)<span
style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Are
there any obvious flaws with this approach I should know about before
attempting it?<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:24.75pt;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>2)<span
style='font:7.0pt "Times New Roman"'> </span></span><![endif]>What
would I have to do to ensure that both copies of the file did not hash to the
same node in the primary and secondary aggregates? My initial thought was that
a matter of having the subvolumes be listed in a different order on one
distribute translator vs. the other (say, in one the subvolumes are listed in alphabetical
order while in the other they are listed in reverse alphabetical order)<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:24.75pt;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>3)<span
style='font:7.0pt "Times New Roman"'> </span></span><![endif]>If
I add or remove a subvolume from the distribute translator in such a way as to
alter the position of other subvolumes in the list (say, when adding a new
subvolume in the middle of an alphabetized list), will this totally mess up the
file-to-host hashing and make my existing files inaccessible?<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:24.75pt'><o:p> </o:p></p>
<p class=MsoNormal>Thank you,<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:24.75pt'><o:p> </o:p></p>
<p class=MsoNormal>-- Marcio<o:p></o:p></p>
</div>
</body>
</html>