<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="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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:"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:0cm;
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;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@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]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">If it’s any help, Simon, I had a very similar problem, and I set
</span><b><span style="font-size:12.0pt;color:#2F2F2F">afmDirLookupRefreshInterval</span></b><span style="font-size:10.0pt">and
</span><b><span style="font-size:12.0pt;color:#2F2F2F">afmFileLookupRefreshInterval
</span></b><span style="mso-fareast-language:EN-US">to one day on an AFM cache fileset which only had software on it. It did make a difference to the users. And if you are really desperate to push an application upgrade to the cache fileset, there are other
ways to do it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Sandra<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> gpfsug-discuss-bounces@spectrumscale.org [mailto:gpfsug-discuss-bounces@spectrumscale.org]
<b>On Behalf Of </b>Venkateswara R Puvvada<br>
<b>Sent:</b> 30 May 2018 15:30<br>
<b>To:</b> gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>
<b>Subject:</b> Re: [gpfsug-discuss] AFM negative file caching<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">>I wasn’t sure if </span><b><span style="font-size:12.0pt;color:#2F2F2F">afmDirLookupRefreshInterval</span></b><span style="font-size:10.0pt">and
</span><b><span style="font-size:12.0pt;color:#2F2F2F">afmFileLookupRefreshInterval</span></b><span style="font-size:10.0pt">would be the right thing if it’s a file/directory that doesn’t exist?</span><br>
<br>
<span style="font-size:10.0pt">These refresh intervals applies to all the lookups and not just for negative lookups.
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">For working around in AFM itself, you could try setting these refresh intervals to higher value if cache does not need to validate with home often.</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">~Venkat (<a href="mailto:vpuvvada@in.ibm.com">vpuvvada@in.ibm.com</a>)</span><br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><a href="mailto:david_johnson@brown.edu">david_johnson@brown.edu</a></span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">gpfsug main discussion list <<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.org</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">05/30/2018 06:14 PM</span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">Re: [gpfsug-discuss] AFM negative file caching</span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">gpfsug-discuss-bounces@spectrumscale.org</a></span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<tt><span style="font-size:10.0pt">Another possible workaround would be to add wrappers for these apps and only add the AFM based gpfs directory to the LD_LIBARY_PATH when about to launch the app.
</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
<tt> -- ddj</tt><br>
<tt>Dave Johnson</tt><br>
<br>
<tt>> On May 30, 2018, at 8:26 AM, Peter Serocka <<a href="mailto:peserocka@gmail.com">peserocka@gmail.com</a>> wrote:</tt><br>
<tt>> </tt><br>
<tt>> As a quick means, why not adding /usr/lib64 at the beginning of LD_LIBRARY_PATH?</tt><br>
<tt>> </tt><br>
<tt>> (Not to get started on using LD_LIBRARY_PATH in the first place…)</tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> — Peter</tt><br>
<tt>> </tt><br>
<tt>>> On 2018 May 30 Wed, at 13:52, Simon Thompson (IT Research Support) <<a href="mailto:S.J.Thompson@bham.ac.uk">S.J.Thompson@bham.ac.uk</a>> wrote:</tt><br>
<tt>>> </tt><br>
<tt>>> Hi All,</tt><br>
<tt>>> </tt><br>
<tt>>> We have a file-set which is an AFM fileset and contains installed software.</tt><br>
<tt>>> </tt><br>
<tt>>> We’ve been experiencing some performance issues with workloads when this is running and think this is down to LD_LIBRARY_PATH being set to the software installed in the AFM cache, e.g.</tt><br>
<tt>>> </tt><br>
<tt>>> /gpfs/apps/somesoftware/v1.2/lib</tt><br>
<tt>>> </tt><br>
<tt>>> Subsequently when you run (e.g.) “who” on the system, LD_LIBRARY_PATH is being searched for e.g. libnss_ldap, which is in /usr/lib64. We’re assuming that AFM is checking with home each time the directory is processed (and other sub directories like lib/tls)
and that each time AFM is checking for the file’s existence at home. Is there a way to change the negative cache at all on AFM for this one file-set? (e.g as you might with NFS). The file-set only has applications so changes are pretty rare and so a 10 min
or so check would be fine with me.</tt><br>
<tt>>> </tt><br>
<tt>>> Thanks</tt><br>
<tt>>> </tt><br>
<tt>>> Simon </tt><br>
<tt>>> </tt><br>
<tt>>> _______________________________________________</tt><br>
<tt>>> gpfsug-discuss mailing list</tt><br>
<tt>>> gpfsug-discuss at spectrumscale.org</tt><br>
<tt>>> </tt></span><a href="https://clicktime.symantec.com/a/1/TtPgHxPdZETZyZD6VKdvDXDlZoAcJSTniZmcYktzays=?d=8nDD9F3Rpnpe15wDwwfRZSw3XF9WlBzx-5NMAiHtzlluhNF6Qfyvx5qBpPqP80bb2jOlRGC0kbZtnYit97--GU3bpXC-0OWm1d8u-zN-Brvf-KNUxZnaPYy30_fZO3ADaBs4VgC40HmbbHjQbxt4hfJDfeL5nf0US1oMy8GcG5F2upO20hy8ejRqGpk0Gd-cpynHDV1q0k6QJJjKEFZghUYEGdTXzWJDDPJ6zCPKhfrCf0Jh-onsd_ncUL2kIbHsBFX4IoEiBlb_XPBpaAMKmbvYsd4PgQtFWs81hVHcXUFc7unPz8Z3zK9q4Xz23T9xpJilERzw05Gmc6HTUh-GhBOVMtTzL0a53v5ORbySJIo1_PBqGQKL21NRtwQP86Zf4lCcpHYN8Yqjf0JFxlvMAWQaLpZd5xfzz6LAJjNPPeTqbLUC4wLn9mAQdWyLbKXza-fIkbX23Y6ODw%3D%3D&u=http%3A%2F%2Fgpfsug.org%2Fmailman%2Flistinfo%2Fgpfsug-discuss"><tt><span style="font-size:10.0pt">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>> </tt><br>
<tt>> _______________________________________________</tt><br>
<tt>> gpfsug-discuss mailing list</tt><br>
<tt>> gpfsug-discuss at spectrumscale.org</tt><br>
<tt>> </tt></span><a href="https://clicktime.symantec.com/a/1/TtPgHxPdZETZyZD6VKdvDXDlZoAcJSTniZmcYktzays=?d=8nDD9F3Rpnpe15wDwwfRZSw3XF9WlBzx-5NMAiHtzlluhNF6Qfyvx5qBpPqP80bb2jOlRGC0kbZtnYit97--GU3bpXC-0OWm1d8u-zN-Brvf-KNUxZnaPYy30_fZO3ADaBs4VgC40HmbbHjQbxt4hfJDfeL5nf0US1oMy8GcG5F2upO20hy8ejRqGpk0Gd-cpynHDV1q0k6QJJjKEFZghUYEGdTXzWJDDPJ6zCPKhfrCf0Jh-onsd_ncUL2kIbHsBFX4IoEiBlb_XPBpaAMKmbvYsd4PgQtFWs81hVHcXUFc7unPz8Z3zK9q4Xz23T9xpJilERzw05Gmc6HTUh-GhBOVMtTzL0a53v5ORbySJIo1_PBqGQKL21NRtwQP86Zf4lCcpHYN8Yqjf0JFxlvMAWQaLpZd5xfzz6LAJjNPPeTqbLUC4wLn9mAQdWyLbKXza-fIkbX23Y6ODw%3D%3D&u=http%3A%2F%2Fgpfsug.org%2Fmailman%2Flistinfo%2Fgpfsug-discuss"><tt><span style="font-size:10.0pt">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>_______________________________________________</tt><br>
<tt>gpfsug-discuss mailing list</tt><br>
<tt>gpfsug-discuss at spectrumscale.org</tt><br>
</span><a href="https://clicktime.symantec.com/a/1/TtPgHxPdZETZyZD6VKdvDXDlZoAcJSTniZmcYktzays=?d=8nDD9F3Rpnpe15wDwwfRZSw3XF9WlBzx-5NMAiHtzlluhNF6Qfyvx5qBpPqP80bb2jOlRGC0kbZtnYit97--GU3bpXC-0OWm1d8u-zN-Brvf-KNUxZnaPYy30_fZO3ADaBs4VgC40HmbbHjQbxt4hfJDfeL5nf0US1oMy8GcG5F2upO20hy8ejRqGpk0Gd-cpynHDV1q0k6QJJjKEFZghUYEGdTXzWJDDPJ6zCPKhfrCf0Jh-onsd_ncUL2kIbHsBFX4IoEiBlb_XPBpaAMKmbvYsd4PgQtFWs81hVHcXUFc7unPz8Z3zK9q4Xz23T9xpJilERzw05Gmc6HTUh-GhBOVMtTzL0a53v5ORbySJIo1_PBqGQKL21NRtwQP86Zf4lCcpHYN8Yqjf0JFxlvMAWQaLpZd5xfzz6LAJjNPPeTqbLUC4wLn9mAQdWyLbKXza-fIkbX23Y6ODw%3D%3D&u=http%3A%2F%2Fgpfsug.org%2Fmailman%2Flistinfo%2Fgpfsug-discuss"><tt><span style="font-size:10.0pt">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
</span><br>
<br>
<o:p></o:p></p>
</div>
<hr>
<p class="{Imprint.UniqueID}" style="FONT-SIZE: 8pt"><font face="Arial">AstraZeneca UK Limited is a company incorporated in England and Wales with registered number:03674842 and its registered office at 1 Francis Crick Avenue, Cambridge Biomedical Campus, Cambridge,
CB2 0AA.</font></p>
<p class="{Imprint.UniqueID}" style="FONT-SIZE: 8pt"><font face="Arial" size="1"></font></p>
<p class="{Imprint.UniqueID}" style="FONT-SIZE: 8pt"><font face="Arial">This e-mail and its attachments are intended for the above named recipient only and may contain confidential and privileged information. If they have come to you in error, you must not
copy or show them to anyone; instead, please reply to this e-mail, highlighting the error to the sender and then immediately delete the message. For information about how AstraZeneca UK Limited and its affiliates may process information, personal data and
monitor communications, please see our privacy notice at <a href="https://www.astrazeneca.com">
www.astrazeneca.com</a></font></p>
</body>
</html>