<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I’ve got a small Lustre lab setup with the following server specs:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2 X OSS’S:<o:p></o:p></p><p class=MsoNormal>Dual Xeon 5410<o:p></o:p></p><p class=MsoNormal>4X1TB HDD @ RAID10<o:p></o:p></p><p class=MsoNormal>16G of RAM<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1 X MDS:<o:p></o:p></p><p class=MsoNormal>Dual Xeon 5410<o:p></o:p></p><p class=MsoNormal>4X1TB HDD @ RAID10<o:p></o:p></p><p class=MsoNormal>16G of RAM<o:p></o:p></p><p class=MsoNormal>(I know this may be overkill, but I included it just for reference)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We plan on running virtual instances and using this Lustre storage pool for each instance’s storage. Right now, no striping is enabled (until we figure out the redundancy side), but what I’m wondering is how the metadata handles the move (if at all) of data if one of the OSS’s runs out of data.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Here’s a scenario:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Instance #1 -> MDS sends to OSS1<o:p></o:p></p><p class=MsoNormal>Instance #2 -> MDS sends to OSS2<o:p></o:p></p><p class=MsoNormal>Instance #3 -> MDS sends to OSS1<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Suddenly both instance #1 and #3 consume all available storage on OSS1. What happens then? Does the MDS send any further writes to OSS2? As far as I know there is no way to move around data using the MDS to a different OSS, so I’m a bit confused. Striping may slow this specific scenario down, but the lack of resiliency is something we’re still testing – dabbling with DRBD.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks in advance for any comments or suggestions <span style='font-family:Wingdings'>J</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>