<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:0cm;
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</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-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hi,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’m interested to find out what possible solutions there
are for upgrading storage hardware within a cluster over time, either following
a failure or just through nodes coming to the end of their normal working life.
We would expect a cluster to exist for many years whereas the individual nodes
may only last a few years each. Ideally it should be possible to migrate data
off an OST as required but there doesn’t appear to be anything in the
manual which covers this use case specifically.<o:p></o:p></p>
<pre><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></pre><pre><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>The closest thing seems to be in section </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>4.3.11 of the manual “Removing and Restoring OSTs” (http://manual.lustre.org/manual/LustreManual18_HTML/ConfiguringLustre.html#50532400_57420):<o:p></o:p></span></pre>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>“OSTs can be removed from and restored to a Lustre
file system. Currently in Lustre, removing an OST really means that the OST is
'deactivated' in the file system, not permanently removed. A removed OST still
appears in the file system; do not create a new OST with the same name.”<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thus one route to migration to new hardware could be to
remove an OST (making sure the name is not reused) then use step 2.5 in section
4.3.11.1 to copy to the _<i>new</i>_ hardware, rather than recovering to the
same hardware.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Does anyone have experience with this type of use case or
knowledge of alternative ways of handling this which they could describe for
me?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Many thanks,<o:p></o:p></p>
<p class=MsoNormal>Daniel.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>*******************************************************<o:p></o:p></p>
<p class=MsoNormal>British Atmospheric Data Centre<o:p></o:p></p>
<p class=MsoNormal>STFC Rutherford Appleton Laboratory<o:p></o:p></p>
<p class=MsoNormal>Chilton, Didcot, Oxfordshire, OX11 0QX<o:p></o:p></p>
<p class=MsoNormal>*******************************************************<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<br><p>--
<BR>Scanned by iCritical.
</p>
<br></body>
</html>