<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:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@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:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Only compelling reason for new cluster would be old hardware is EOL or no longer want to pay maintenance on it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black"><gpfsug-discuss-bounces@spectrumscale.org> on behalf of Marc A Kaplan <makaplan@us.ibm.com><br>
<b>Reply-To: </b>gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>
<b>Date: </b>Tuesday, October 11, 2016 at 2:58 PM<br>
<b>To: </b>gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>
<b>Subject: </b>Re: [gpfsug-discuss] Hardware refresh<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"sans-serif","serif"">New FS? Yes there are some good reasons. </span><br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">New cluster? I did not see a compelling argument either way.</span><br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">"Mark.Bush@siriuscom.com" <Mark.Bush@siriuscom.com></span><br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">gpfsug main discussion list <gpfsug-discuss@spectrumscale.org></span><br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">10/11/2016 03:34 PM</span><br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">Re: [gpfsug-discuss] Hardware refresh</span><br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Sent by: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">gpfsug-discuss-bounces@spectrumscale.org</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri">Ok. I think I am hearing that a new cluster with a new FS and copying data from old to new cluster is the best way forward. Thanks everyone for your input. </span><br>
<span style="font-size:10.0pt;font-family:Calibri"> </span><br>
<b><span style="font-family:Calibri">From: </span></b><span style="font-family:Calibri"><gpfsug-discuss-bounces@spectrumscale.org> on behalf of Yuri L Volobuev <volobuev@us.ibm.com><b><br>
Reply-To: </b>gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><b><br>
Date: </b>Tuesday, October 11, 2016 at 12:22 PM<b><br>
To: </b>gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><b><br>
Subject: </b>Re: [gpfsug-discuss] Hardware refresh</span><br>
<o:p></o:p></p>
<p>This depends on the committed cluster version level (minReleaseLevel) and file system format. Since NFSv2 is an on-disk format change, older code wouldn't be able to understand what it is, and thus if there's a possibility of a downlevel node looking at
the NSD, the NFSv1 format is going to be used. The code does NSDv1<->NSDv2 conversions under the covers as needed when adding an empty NSD to a file system.<br>
<br>
I'd strongly recommend getting a fresh start by formatting a new file system. Many things have changed over the course of the last few years. In particular, having a 4K-aligned file system can be a pretty big deal, depending on what hardware one is going to
deploy in the future, and this is something that can't be bolted onto an existing file system. Having 4K inodes is very handy for many reasons. New directory format and NSD format changes are attractive, too. And disks generally tend to get larger with time,
and at some point you may want to add a disk to an existing storage pool that's larger than the existing allocation map format allows. Obviously, it's more hassle to migrate data to a new file system, as opposed to extending an existing one. In a perfect world,
GPFS would offer a conversion tool that seamlessly and robustly converts old file systems, making them as good as new, but in the real world such a tool doesn't exist. Getting a clean slate by formatting a new file system every few years is a good long-term
investment of time, although it comes front-loaded with extra work.<br>
<br>
yuri<br>
<br>
<img width="16" height="16" id="_x0000_i1026" src="cid:image001.gif@01D223E2.68011C50" alt="active hide details for Aaron Knister ---10/10/2016 04:45:31 PM---Can on"><span style="color:#424282">Aaron Knister ---10/10/2016 04:45:31 PM---Can one format NSDv2
NSDs and put them in a filesystem with NSDv1 NSD's? -Aaron</span><br>
<span style="font-size:10.0pt;color:#5F5F5F"><br>
From: </span><span style="font-size:10.0pt">Aaron Knister <aaron.s.knister@nasa.gov><span style="color:#5F5F5F"><br>
To: </span><gpfsug-discuss@spectrumscale.org>, <span style="color:#5F5F5F"><br>
Date: </span>10/10/2016 04:45 PM<span style="color:#5F5F5F"><br>
Subject: </span>Re: [gpfsug-discuss] Hardware refresh<span style="color:#5F5F5F"><br>
Sent by: </span>gpfsug-discuss-bounces@spectrumscale.org</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
Can one format NSDv2 NSDs and put them in a filesystem with NSDv1 NSD's?<br>
<br>
-Aaron<br>
<br>
On 10/10/16 7:40 PM, Luis Bolinches wrote:<br>
> Hi<br>
><br>
> Creating a new FS sounds like a best way to go. NSDv2 being a very good<br>
> reason to do so.<br>
><br>
> AFM for migrations is quite good, latest versions allows to use NSD<br>
> protocol for mounts as well. Olaf did a great job explaining this<br>
> scenario on the redbook chapter 6<br>
><br>
> </span><a href="http://www.redbooks.ibm.com/abstracts/sg248254.html?Open"><span style="font-size:10.0pt;font-family:"Courier New"">http://www.redbooks.ibm.com/abstracts/sg248254.html?Open</span></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
><br>
> --<br>
> Cheers<br>
><br>
> On 10 Oct 2016, at 23.05, Buterbaugh, Kevin L<br>
> <Kevin.Buterbaugh@Vanderbilt.Edu<br>
> <</span><a href="mailto:Kevin.Buterbaugh@Vanderbilt.Edu"><span style="font-size:10.0pt;font-family:"Courier New"">mailto:Kevin.Buterbaugh@Vanderbilt.Edu</span></a><span style="font-size:10.0pt;font-family:"Courier New"">>> wrote:<br>
><br>
>> Hi Mark,<br>
>><br>
>> The last time we did something like this was 2010 (we’re doing rolling<br>
>> refreshes now), so there are probably lots of better ways to do this<br>
>> than what we did, but we:<br>
>><br>
>> 1) set up the new hardware<br>
>> 2) created new filesystems (so that we could make adjustments we<br>
>> wanted to make that can only be made at FS creation time)<br>
>> 3) used rsync to make a 1st pass copy of everything<br>
>> 4) coordinated a time with users / groups to do a 2nd rsync when they<br>
>> weren’t active<br>
>> 5) used symbolic links during the transition (i.e. rm -rvf<br>
>> /gpfs0/home/joeuser; ln -s /gpfs2/home/joeuser /gpfs0/home/joeuser)<br>
>> 6) once everybody was migrated, updated the symlinks (i.e. /home<br>
>> became a symlink to /gpfs2/home)<br>
>><br>
>> HTHAL…<br>
>><br>
>> Kevin<br>
>><br>
>>> On Oct 10, 2016, at 2:56 PM, Mark.Bush@siriuscom.com<br>
>>> <</span><a href="mailto:Mark.Bush@siriuscom.com"><span style="font-size:10.0pt;font-family:"Courier New"">mailto:Mark.Bush@siriuscom.com</span></a><span style="font-size:10.0pt;font-family:"Courier New"">> wrote:<br>
>>><br>
>>> Have a very old cluster built on IBM X3650’s and DS3500. Need to<br>
>>> refresh hardware. Any lessons learned in this process? Is it<br>
>>> easiest to just build new cluster and then use AFM? Add to existing<br>
>>> cluster then decommission nodes? What is the recommended process for<br>
>>> this?<br>
>>><br>
>>><br>
>>> Mark<br>
>>><br>
>>> This message (including any attachments) is intended only for the use<br>
>>> of the individual or entity to which it is addressed and may contain<br>
>>> information that is non-public, proprietary, privileged,<br>
>>> confidential, and exempt from disclosure under applicable law. If you<br>
>>> are not the intended recipient, you are hereby notified that any use,<br>
>>> dissemination, distribution, or copying of this communication is<br>
>>> strictly prohibited. This message may be viewed by parties at Sirius<br>
>>> Computer Solutions other than those named in the message header. This<br>
>>> message does not contain an official representation of Sirius<br>
>>> Computer Solutions. If you have received this communication in error,<br>
>>> notify Sirius Computer Solutions immediately and (i) destroy this<br>
>>> message if a facsimile or (ii) delete this message immediately if<br>
>>> this is an electronic communication. Thank you.<br>
>>><br>
>>> Sirius Computer Solutions <</span><a href="http://www.siriuscom.com/"><span style="font-size:10.0pt;font-family:"Courier New"">http://www.siriuscom.com/</span></a><span style="font-size:10.0pt;font-family:"Courier New"">><br>
>>> _______________________________________________<br>
>>> gpfsug-discuss mailing list<br>
>>> gpfsug-discuss at spectrumscale.org <</span><a href="http://spectrumscale.org/"><span style="font-size:10.0pt;font-family:"Courier New"">http://spectrumscale.org/</span></a><span style="font-size:10.0pt;font-family:"Courier New"">><br>
>>> </span><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><span style="font-size:10.0pt;font-family:"Courier New"">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
>><br>
>> —<br>
>> Kevin Buterbaugh - Senior System Administrator<br>
>> Vanderbilt University - Advanced Computing Center for Research and<br>
>> Education<br>
>> Kevin.Buterbaugh@vanderbilt.edu<br>
>> <</span><a href="mailto:Kevin.Buterbaugh@vanderbilt.edu"><span style="font-size:10.0pt;font-family:"Courier New"">mailto:Kevin.Buterbaugh@vanderbilt.edu</span></a><span style="font-size:10.0pt;font-family:"Courier New"">> - (615)875-9633<br>
>><br>
>><br>
>><br>
><br>
> Ellei edellä ole toisin mainittu: / Unless stated otherwise above:<br>
> Oy IBM Finland Ab<br>
> PL 265, 00101 Helsinki, Finland<br>
> Business ID, Y-tunnus: 0195876-3<br>
> Registered in Finland<br>
><br>
><br>
><br>
> _______________________________________________<br>
> gpfsug-discuss mailing list<br>
> gpfsug-discuss at spectrumscale.org<br>
> </span><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><span style="font-size:10.0pt;font-family:"Courier New"">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
><br>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at spectrumscale.org<u><span style="color:blue"><br>
</span></u></span><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><span style="font-size:10.0pt;font-family:"Courier New"">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
</span><br>
<br>
<o:p></o:p></p>
<p><span style="font-size:7.5pt;font-family:Cambria">This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential,
and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. This message may be viewed by parties at Sirius
Computer Solutions other than those named in the message header. This message does not contain an official representation of Sirius Computer Solutions. If you have received this communication in error, notify Sirius Computer Solutions immediately and (i) destroy
this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
</span><o:p></o:p></p>
<p><a href="http://www.siriuscom.com/"><b><span style="font-size:10.0pt;font-family:Calibri">Sirius Computer Solutions</span></b></a>
<tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>gpfsug-discuss mailing list</tt><br>
<tt>gpfsug-discuss at spectrumscale.org</tt><br>
</span><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><span style="font-size:10.0pt">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></tt></a><o:p></o:p></p>
<p><o:p> </o:p></p>
</div>
</body>
</html>