<html><body><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" src="cid:1__=07BB0ADADFCDD4C98f9e8a93df938690918c07B@" border="0" alt="Inactive hide details for Aaron Knister ---10/10/2016 04:45:31 PM---Can one format NSDv2 NSDs and put them in a filesystem with"><font 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</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Aaron Knister <aaron.s.knister@nasa.gov></font><br><font size="2" color="#5F5F5F">To: </font><font size="2"><gpfsug-discuss@spectrumscale.org>, </font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">10/10/2016 04:45 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [gpfsug-discuss] Hardware refresh</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt>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>> </tt><tt><a href="http://www.redbooks.ibm.com/abstracts/sg248254.html?Open">http://www.redbooks.ibm.com/abstracts/sg248254.html?Open</a></tt><tt><br>><br>> --<br>> Cheers<br>><br>> On 10 Oct 2016, at 23.05, Buterbaugh, Kevin L<br>> <Kevin.Buterbaugh@Vanderbilt.Edu<br>> <</tt><tt><a href="mailto:Kevin.Buterbaugh@Vanderbilt.Edu">mailto:Kevin.Buterbaugh@Vanderbilt.Edu</a></tt><tt>>> 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>>>> <</tt><tt><a href="mailto:Mark.Bush@siriuscom.com">mailto:Mark.Bush@siriuscom.com</a></tt><tt>> 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 <</tt><tt><a href="http://www.siriuscom.com/">http://www.siriuscom.com/</a></tt><tt>><br>>>> _______________________________________________<br>>>> gpfsug-discuss mailing list<br>>>> gpfsug-discuss at spectrumscale.org <</tt><tt><a href="http://spectrumscale.org/">http://spectrumscale.org/</a></tt><tt>><br>>>> </tt><tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></tt><tt><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>>> <</tt><tt><a href="mailto:Kevin.Buterbaugh@vanderbilt.edu">mailto:Kevin.Buterbaugh@vanderbilt.edu</a></tt><tt>> - (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>> </tt><tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></tt><tt><br>><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></tt><tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></tt><tt><br><br></tt><br><BR>
</body></html>