<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Your observation is correct! There’s usually another step, though:</div><div class=""><br class=""></div>mmcrnsd creates each NSD on the first server in the list, so if you “stripe” the servers you have to know the device name for that NSD on the node that is first in the server list for that NSD. It is usually less work to pick one node, create the NSDs and then change them to have a different server order.<div class=""><br class=""></div><div class=""><div class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">-- <br class="">Stephen<br class=""><br class=""><br class=""></div></div>
</div><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 19, 2016, at 10:58 AM, Buterbaugh, Kevin L <<a href="mailto:Kevin.Buterbaugh@vanderbilt.edu" class="">Kevin.Buterbaugh@Vanderbilt.Edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi Ken,
<div class=""><br class="">
</div>
<div class="">Umm, wouldn’t that make that server the primary NSD server for all those NSDs? Granted, you run the mmcrnsd command from one arbitrarily chosen server, but as long as you have the proper device name for the NSD from the NSD server you want to
be primary for it, I’ve never had a problem specifying many different servers first in the list.</div>
<div class=""><br class="">
</div>
<div class="">Or am I completely misunderstanding what you’re saying? Thanks...</div>
<div class=""><br class="">
</div>
<div class="">Kevin</div>
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Dec 19, 2016, at 9:30 AM, Ken Hill <<a href="mailto:kenh@us.ibm.com" class="">kenh@us.ibm.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><font size="2" face="sans-serif" class="">Indeed. It only matters when deploying NSDs. Post-deployment, all luns (NSDs) are labeled - and they are assembled by GPFS.</font><br class="">
<br class="">
<font size="2" face="sans-serif" class="">Keep in mind: If you are deploying multiple NSDs (with multiple servers) - you'll need to pick one server to work with... Use that server to label the luns (mmcrnsd)... In the nsd stanza file - the server you choose
will need to be the first server in the "servers" list.</font><br class="">
<br class="">
<br class="">
<font size="3" color="#8f8f8f" face="Arial" class=""><b class="">Ken Hill</b></font><font size="2" face="Arial" class=""><br class="">
Technical Sales Specialist | Software Defined Solution Sales<br class="">
IBM Systems</font><font size="3" class=""> </font>
<table width="776" style="border-collapse:collapse;" class="">
<tbody class="">
<tr height="8" class="">
<td width="774" colspan="3" bgcolor="#2b2b2c" style="border-style:none none none none;border-color:#F3F3F5;border-width:0px 0px 0px 0px;padding:1px 1px;" class="">
<hr class="">
</td>
</tr>
<tr height="8" class="">
<td width="157" bgcolor="#2b2b2c" style="border-style:none none none none;border-color:#F3F3F5;border-width:0px 0px 0px 0px;padding:1px 1px;" class="">
<font size="1" color="#4181c0" face="Arial" class=""><b class="">Phone:</b></font><font size="1" face="Arial" class="">1-540-207-7270</font><font size="1" color="#4181c0" face="Arial" class=""><b class=""><br class="">
E-mail:</b></font><font size="3" face="Arial" class=""> </font><a href="mailto:kenh@us.ibm.com" target="_blank" class=""><font size="1" color="#5f5f5f" face="Arial" class=""><u class="">kenh@us.ibm.com</u></font></a></td>
<td width="600" bgcolor="#2b2b2c" style="border-style:none none none none;border-color:#F3F3F5;border-width:0px 0px 0px 0px;padding:1px 1px;" class="">
<div align="right" class=""><a href="http://www.ibm.com/us-en/" class=""><span id="cid:_4_C54E0CB8C54E073800553B548525808E" class=""><ATT00001.png></span></a><font size="3" class="">
</font><a href="http://www-03.ibm.com/systems/platformcomputing/products/lsf/" class=""><span id="cid:_4_C54E2AD0C54E073800553B548525808E" class=""><ATT00002.png></span></a><font size="3" class="">
</font><a href="http://www-03.ibm.com/systems/platformcomputing/products/high-performance-services/index.html" class=""><span id="cid:_4_C54E2CF8C54E073800553B548525808E" class=""><ATT00003.png></span></a><font size="3" class="">
</font><a href="http://www-03.ibm.com/systems/platformcomputing/products/symphony/index.html" class=""><span id="cid:_4_C54E3114C54E073800553B548525808E" class=""><ATT00004.png></span></a><font size="3" class="">
</font><a href="http://www-03.ibm.com/systems/storage/spectrum/" class=""><span id="cid:_4_C54E358CC54E073800553B548525808E" class=""><ATT00005.png></span></a><font size="3" class="">
</font><a href="http://www-01.ibm.com/software/tivoli/csi/cloud-storage/" class=""><span id="cid:_4_C54E3A04C54E073800553B548525808E" class=""><ATT00006.png></span></a><font size="3" class="">
</font><a href="http://www-01.ibm.com/software/tivoli/csi/backup-recovery/" class=""><span id="cid:_4_C54E3E7CC54E073800553B548525808E" class=""><ATT00007.png></span></a><font size="3" class="">
</font><a href="http://www-03.ibm.com/systems/storage/tape/ltfs/index.html" class=""><span id="cid:_4_C54E42F4C54E073800553B548525808E" class=""><ATT00008.png></span></a><font size="3" class="">
</font><a href="http://www-03.ibm.com/systems/storage/spectrum/" class=""><span id="cid:_4_C54E476CC54E073800553B548525808E" class=""><ATT00009.png></span></a><font size="3" class="">
</font><a href="http://www-03.ibm.com/systems/storage/spectrum/scale/" class=""><span id="cid:_4_C54E4BE4C54E073800553B548525808E" class=""><ATT00010.png></span></a><font size="3" class="">
</font><a href="https://www.ibm.com/marketplace/cloud/object-storage/us/en-us" class=""><span id="cid:_4_C54E505CC54E073800553B548525808E" class=""><ATT00011.png></span></a><font size="3" class="">
</font><font size="1" face="Arial" class=""><br class="">
<br class="">
2300 Dulles Station Blvd<br class="">
Herndon, VA 20171-6133<br class="">
United States</font></div>
</td>
<td width="11" bgcolor="#2b2b2c" valign="top" style="border-style:none none none none;border-color:#F3F3F5;border-width:0px 0px 0px 0px;padding:1px 1px;" class="">
</td>
</tr>
</tbody>
</table>
<br class="">
<br class="">
<font size="3" class=""><br class="">
<br class="">
<br class="">
<br class="">
<br class="">
</font><br class="">
<br class="">
<br class="">
<font size="1" color="#5f5f5f" face="sans-serif" class="">From: </font><font size="1" face="sans-serif" class="">"Daniel Kidger" <<a href="mailto:daniel.kidger@uk.ibm.com" class="">daniel.kidger@uk.ibm.com</a>></font><br class="">
<font size="1" color="#5f5f5f" face="sans-serif" class="">To: </font><font size="1" face="sans-serif" class="">"gpfsug main discussion list" <<a href="mailto:gpfsug-discuss@spectrumscale.org" class="">gpfsug-discuss@spectrumscale.org</a>></font><br class="">
<font size="1" color="#5f5f5f" face="sans-serif" class="">Cc: </font><font size="1" face="sans-serif" class="">"gpfsug main discussion list" <<a href="mailto:gpfsug-discuss@spectrumscale.org" class="">gpfsug-discuss@spectrumscale.org</a>></font><br class="">
<font size="1" color="#5f5f5f" face="sans-serif" class="">Date: </font><font size="1" face="sans-serif" class="">12/19/2016 06:42 AM</font><br class="">
<font size="1" color="#5f5f5f" face="sans-serif" class="">Subject: </font><font size="1" face="sans-serif" class="">Re: [gpfsug-discuss] translating /dev device into nsd name</font><br class="">
<font size="1" color="#5f5f5f" face="sans-serif" class="">Sent by: </font><font size="1" face="sans-serif" class=""><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org" class="">gpfsug-discuss-bounces@spectrumscale.org</a></font><br class="">
<hr noshade="" class="">
<br class="">
<br class="">
<br class="">
<font size="3" class=""><i class="">Valdis wrote:</i></font><br class="">
<font size="3" class=""><i class="">Keep in mind that if you have multiple NSD servers in the cluster, there<br class="">
is *no* guarantee that the names for a device will be consistent across<br class="">
the servers, or across reboots. And when multipath is involved, you may<br class="">
have 4 or 8 or even more names for the same device....</i><br class="">
<br class="">
Indeed the is whole greatness about NSDs (and in passing why Lustre can be much more tricky to safely manage.)</font><br class="">
<font size="3" class="">Once a lun is "labelled" as an NSD then that NSD name is all you need to care about as the /dev entries can now freely change on reboot or differ across nodes. Indeed if you connect an arbitrary node to an NSD disk via a SAN cable, gpfs
will recognise it and use it as a shortcut to that lun.</font><br class="">
<br class="">
<font size="3" class="">Finally recall that in the NSD stanza file the /dev entry is only matched for on the first of the listed NSD servers; the other NSD servers will discover and learn which NSD this is, ignoring the /dev value in this stanza.</font><br class="">
<font size="3" class=""><br class="">
Daniel<br class="">
<br class="">
IBM Spectrum Storage Software</font><font size="3" color="blue" class=""><u class=""><br class="">
</u></font><a href="tel:+44%207818%20522266" class=""><font size="3" color="blue" class=""><u class="">+44 (0)7818 522266</u></font></a><font size="3" class=""><br class="">
Sent from my iPad using IBM Verse<br class="">
<br class="">
<br class="">
</font>
<hr class="">
<font size="3" class="">On 17 Dec 2016, 21:43:00, <a href="mailto:Valdis.Kletnieks@vt.edu" class="">
Valdis.Kletnieks@vt.edu</a> wrote:<br class="">
<br class="">
From: <a href="mailto:Valdis.Kletnieks@vt.edu" class="">Valdis.Kletnieks@vt.edu</a><br class="">
To: <a href="mailto:gpfsug-discuss@spectrumscale.org" class="">gpfsug-discuss@spectrumscale.org</a><br class="">
Cc: <br class="">
Date: 17 Dec 2016 21:43:00<br class="">
Subject: Re: [gpfsug-discuss] translating /dev device into nsd name<br class="">
</font><br class="">
<font size="3" class="">On Fri, 16 Dec 2016 23:24:34 -0500, Aaron Knister said:<br class="">
> that I can then parse and map the nsd id to the nsd name. I hesitate<br class="">
> calling ts* commands directly and I admit it's perhaps an irrational<br class="">
> fear, but I associate the -D flag with "delete" in my head and am afraid<br class="">
> that some day -D may be just that and *poof* there go my NSD descriptors.<br class="">
Others have mentioned mmlsdnsd -m and -X<br class="">
Keep in mind that if you have multiple NSD servers in the cluster, there<br class="">
is *no* guarantee that the names for a device will be consistent across<br class="">
the servers, or across reboots. And when multipath is involved, you may<br class="">
have 4 or 8 or even more names for the same device....<br class="">
_______________________________________________<br class="">
gpfsug-discuss mailing list<br class="">
gpfsug-discuss at <a href="http://spectrumscale.org/" class="">spectrumscale.org</a><br class="">
</font><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" class=""><font size="3" class="">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></a><br class="">
<font size="3" class="">Unless stated otherwise above:<br class="">
IBM United Kingdom Limited - Registered in England and Wales with number 741598. <br class="">
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU<br class="">
</font><tt class=""><font size="2" class="">_______________________________________________<br class="">
gpfsug-discuss mailing list<br class="">
gpfsug-discuss at <a href="http://spectrumscale.org/" class="">spectrumscale.org</a><br class="">
</font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" class=""><tt class=""><font size="2" class="">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt class=""><font size="2" class=""><br class="">
</font></tt><br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
gpfsug-discuss mailing list<br class="">
gpfsug-discuss at <a href="http://spectrumscale.org/" class="">spectrumscale.org</a><br class="">
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" class="">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
_______________________________________________<br class="">gpfsug-discuss mailing list<br class="">gpfsug-discuss at <a href="http://spectrumscale.org" class="">spectrumscale.org</a><br class=""><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" class="">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br class=""></div></blockquote></div><br class=""></div></div></body></html>