<font size=2 face="sans-serif">Indeed. It only matters when deploying
NSDs. Post-deployment, all luns (NSDs) are labeled - and they are assembled
by GPFS.</font><br><br><font size=2 face="sans-serif">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><br><br><font size=3 color=#8f8f8f face="Arial"><b>Ken Hill</b></font><font size=2 face="Arial"><br>Technical Sales Specialist | Software Defined Solution Sales<br>IBM Systems</font><font size=3> </font><table width=776 style="border-collapse:collapse;"><tr height=8><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;"><hr><tr height=8><td width=157 bgcolor=#2b2b2c style="border-style:none none none none;border-color:#F3F3F5;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=1 color=#4181c0 face="Arial"><b>Phone:</b></font><font size=1 face="Arial">1-540-207-7270</font><font size=1 color=#4181c0 face="Arial"><b><br>E-mail:</b></font><font size=3 face="Arial"> </font><a href=mailto:kenh@us.ibm.com target=_blank><font size=1 color=#5f5f5f face="Arial"><u>kenh@us.ibm.com</u></font></a><td width=600 bgcolor=#2b2b2c style="border-style:none none none none;border-color:#F3F3F5;border-width:0px 0px 0px 0px;padding:1px 1px;"><div align=right><a href="http://www.ibm.com/us-en/"><img src=cid:_4_C54E0CB8C54E073800553B548525808E style="border:0px solid;"></a><font size=3>
</font><a href="http://www-03.ibm.com/systems/platformcomputing/products/lsf/"><img src=cid:_4_C54E2AD0C54E073800553B548525808E style="border:0px solid;"></a><font size=3>
</font><a href="http://www-03.ibm.com/systems/platformcomputing/products/high-performance-services/index.html"><img src=cid:_4_C54E2CF8C54E073800553B548525808E style="border:0px solid;"></a><font size=3>
</font><a href="http://www-03.ibm.com/systems/platformcomputing/products/symphony/index.html"><img src=cid:_4_C54E3114C54E073800553B548525808E style="border:0px solid;"></a><font size=3>
</font><a href="http://www-03.ibm.com/systems/storage/spectrum/"><img src=cid:_4_C54E358CC54E073800553B548525808E style="border:0px solid;"></a><font size=3>
</font><a href="http://www-01.ibm.com/software/tivoli/csi/cloud-storage/"><img src=cid:_4_C54E3A04C54E073800553B548525808E style="border:0px solid;"></a><font size=3>
</font><a href="http://www-01.ibm.com/software/tivoli/csi/backup-recovery/"><img src=cid:_4_C54E3E7CC54E073800553B548525808E style="border:0px solid;"></a><font size=3>
</font><a href="http://www-03.ibm.com/systems/storage/tape/ltfs/index.html"><img src=cid:_4_C54E42F4C54E073800553B548525808E style="border:0px solid;"></a><font size=3>
</font><a href="http://www-03.ibm.com/systems/storage/spectrum/"><img src=cid:_4_C54E476CC54E073800553B548525808E style="border:0px solid;"></a><font size=3>
</font><a href="http://www-03.ibm.com/systems/storage/spectrum/scale/"><img src=cid:_4_C54E4BE4C54E073800553B548525808E style="border:0px solid;"></a><font size=3>
</font><a href="https://www.ibm.com/marketplace/cloud/object-storage/us/en-us"><img src=cid:_4_C54E505CC54E073800553B548525808E style="border:0px solid;"></a><font size=3>
</font><font size=1 face="Arial"><br><br>2300 Dulles Station Blvd<br>Herndon, VA 20171-6133<br>United States</font></div><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;"></table><br><br><font size=3><br><br><br><br><br></font><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Daniel Kidger"
<daniel.kidger@uk.ibm.com></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"gpfsug main discussion
list" <gpfsug-discuss@spectrumscale.org></font><br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"gpfsug main discussion
list" <gpfsug-discuss@spectrumscale.org></font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">12/19/2016 06:42 AM</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [gpfsug-discuss]
translating /dev device into nsd name</font><br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr noshade><br><br><br><font size=3><i>Valdis wrote:</i></font><br><font size=3><i>Keep in mind that if you have multiple NSD servers
in the cluster, there<br>is *no* guarantee that the names for a device will be consistent across<br>the servers, or across reboots. And when multipath is involved, you
may<br>have 4 or 8 or even more names for the same device....</i><br><br>Indeed the is whole greatness about NSDs (and in passing why Lustre can
be much more tricky to safely manage.)</font><br><font size=3>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><br><font size=3>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><font size=3><br>Daniel<br><br>IBM Spectrum Storage Software</font><font size=3 color=blue><u><br></u></font><a href="tel:+44%207818%20522266"><font size=3 color=blue><u>+44
(0)7818 522266</u></font></a><font size=3><br>Sent from my iPad using IBM Verse<br><br><br></font><hr><font size=3>On 17 Dec 2016, 21:43:00, Valdis.Kletnieks@vt.edu wrote:<br><br>From: Valdis.Kletnieks@vt.edu<br>To: gpfsug-discuss@spectrumscale.org<br>Cc: <br>Date: 17 Dec 2016 21:43:00<br>Subject: Re: [gpfsug-discuss] translating /dev device into nsd name<br></font><br><font size=3>On Fri, 16 Dec 2016 23:24:34 -0500, Aaron Knister said:<br>> that I can then parse and map the nsd id to the nsd name. I hesitate<br>> calling ts* commands directly and I admit it's perhaps an irrational<br>> fear, but I associate the -D flag with "delete" in my head
and am afraid<br>> that some day -D may be just that and *poof* there go my NSD descriptors.<br>Others have mentioned mmlsdnsd -m and -X<br>Keep in mind that if you have multiple NSD servers in the cluster, there<br>is *no* guarantee that the names for a device will be consistent across<br>the servers, or across reboots. And when multipath is involved, you
may<br>have 4 or 8 or even more names for the same device....<br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><font size=3>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></a><br><font size=3>Unless stated otherwise above:<br>IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br>Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU<br></font><tt><font size=2>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br></font></tt><br><br><BR>