<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hey Sandra,<br>
<br>
The mmdynamicmap is used when auto-mounting GPFS on a node the
GPFS software installed (see also /var/mmfs/gen/mmIndirectMap when
gpfs -A is set to 'automount'.)<br>
<br>
<br>
For NFS clients, I like autofs a lot.<br>
There are two types of map, hence an example for each:<br>
<br>
<br>
Direct maps<br>
<br>
/etc/auto.master, add the line:<br>
/- /etc/auto.gpfsnfs<br>
<br>
/etc/auto.gpfsnfs, add the line:<br>
/path/to/mountpoint -fstype=nfs,nfsvers=3
ctdbclustername:/path/to/nfsexport<br>
<br>
<br>
Indirect Maps<br>
<br>
For home directories, you can mount them using an indirect map so
as to only mount the logged in user's home directory.<br>
(or mount them all, using a direct map for their containing
folder)<br>
<br>
/etc/auto.master, add the line:<br>
/path/to/homedirsmount /etc/auto.homedirs<br>
<br>
/etc/auto.homedirs, add the line:<br>
* homeserver:/path/to/homedirs/&<br>
<br>
<br>
<br>
Test in a sandpit.<br>
<br>
I would imagine you might need to make sure that your NFS mount
point reflects the same path as on a GPFS client/server.<br>
<br>
Once you're happy this works, you can push out the maps from your
ldap/puppet/other service.<br>
<br>
I'm sure other folks also have their methods, chime in.<br>
<br>
Regards,<br>
<br>
Jez<br>
---<br>
GPFS UG Chair<br>
<br>
<br>
<br>
On 11/07/13 12:24, McLaughlin, Sandra M wrote:<br>
</div>
<blockquote
cite="mid:1332E4641C13494B98BB1E3DB32CC8150E5CFE03@ukaprdembx02.rd.astrazeneca.net"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<style><!-- /* Style Definitions */ p.dca3ea53-3b15-4956-b62b-477b793a9701, li.dca3ea53-3b15-4956-b62b-477b793a9701, div.dca3ea53-3b15-4956-b62b-477b793a9701, table.dca3ea53-3b15-4956-b62b-477b793a9701Table {margin:0cm; margin-bottom:.0001pt;}div.Section1 {page:Section1;}--></style>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta content="Microsoft Word 12 (filtered medium)"
name="Generator">
<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-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:-3.7pt;
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;}
code
{mso-style-priority:99;
font-family:"Courier New";}
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;}
.MsoPapDefault
{mso-style-type:export-only;
margin-left:-3.7pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal" style="margin-left:0cm">Hi,<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:0cm"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:0cm">I would just like
some opinions on the best way to serve a gpfs file system to
server/workstations which are not directly connected to the
storage.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:0cm"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:0cm">Background: We are
in the process of moving from old storage (approx 20TB); lots
of filesystems – JFS2 on AIX with HACMP. served out with NFS
to a linux cluster and about 150 linux workstations and random
other servers; to new storage (approx 250TB); 2 gpfs
filesystems, Linux NSDs, using ctdb for NFS and Samba. We have
also installed a server for TSM, which is SAN connected to the
gpfs, and have some new compute servers which are also on the
SAN, and therefore have pretty good performance. <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:0cm"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:0cm">Should I still use
the automounter ? Different maps or symbolic links to emulate
the automounter names for the servers that are directly
SAN-connected gpfs clients ? /home/<i>username</i> or whatever
has to work on all systems.<o:p></o:p></p>
<pre style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I found a bit in the gpfs problem determination guide suggesting that there is a way to use an automounter program map for gpfs (<span style="color:black">/usr/lpp/mmfs/bin/mmdynamicmap) </span>but I can’t find any other documentation about it. <o:p></o:p></span></pre>
<pre style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></pre>
<pre style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I would really like to hear how other people with a similar setup are doing this.<o:p></o:p></span></pre>
<pre style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></pre>
<pre style="background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Thanks, Sandra.<span style="color:black"><o:p></o:p></span></span></pre>
<p class="MsoNormal" style="margin-left:0cm"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:0cm"><b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#8B0051">Sandra
McLaughlin<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-left:0cm"><span
style="font-size:8.0pt;font-family:"Arial","sans-serif"">Scientific
Computing Specialist<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:0cm"><span
style="font-size:8.0pt">___________________________________________________</span><span
style="font-size:8.0pt;font-family:"Arial","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:0cm"><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#8B0051">AstraZeneca<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-left:0cm"><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#8B0051">R&D</span></b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#8B0051">
| R&D Information<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:0cm"><span
style="font-size:8.0pt;font-family:"Arial","sans-serif"">30F49,
Mereside, Alderley Park, GB-Macclesfield, SK10 4TG<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:0cm"><span
style="font-size:8.0pt;font-family:"Arial","sans-serif"">Tel
+44 1625 517307<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:0cm"><span
style="font-size:8.0pt;font-family:"Arial","sans-serif""><a
moz-do-not-send="true"
href="mailto:sandra.mclaughlin@astrazeneca.com">sandra.mclaughlin@astrazeneca.com</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:0cm"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:0cm"><o:p> </o:p></p>
</div>
<p class="dca3ea53-3b15-4956-b62b-477b793a9701">
</p>
<hr>
<p class="dca3ea53-3b15-4956-b62b-477b793a9701" style="FONT-SIZE:
8pt"><font face="Arial">AstraZeneca UK Limited is a company
incorporated in England and Wales with registered number:
03674842 and a registered office at 2 Kingdom Street, London,
W2 6BD.</font></p>
<p class="dca3ea53-3b15-4956-b62b-477b793a9701" style="FONT-SIZE:
8pt"><font face="Arial"><strong>Confidentiality Notice: </strong>This
message is private and may contain confidential, proprietary
and legally privileged information. If you have received this
message in error, please notify us and remove it from your
system and note that you must not copy, distribute or take any
action in reliance on it. Any unauthorised use or disclosure
of the contents of this message is not permitted and may be
unlawful.</font></p>
<p class="dca3ea53-3b15-4956-b62b-477b793a9701" style="FONT-SIZE:
8pt"><font face="Arial"><strong>Disclaimer:</strong> Email
messages may be subject to delays, interception, non-delivery
and unauthorised alterations. Therefore, information expressed
in this message is not given or endorsed by AstraZeneca UK
Limited unless otherwise notified by an authorised
representative independent of this message. No contractual
relationship is created by this message by any person unless
specifically indicated by agreement in writing other than
email.</font></p>
<p class="dca3ea53-3b15-4956-b62b-477b793a9701" style="FONT-SIZE:
8pt"><font face="Arial"><strong>Monitoring: </strong>AstraZeneca
UK Limited may monitor email traffic data and content for the
purposes of the prevention and detection of crime, ensuring
the security of our computer systems and checking compliance
with our Code of Conduct and policies.</font> </p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at gpfsug.org
<a class="moz-txt-link-freetext" href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a>
</pre>
</blockquote>
<br>
</body>
</html>