<div dir="ltr">Very likely then the test isn't stressing the system enough. What tunings are you using on your robinhood installation? What tunings on the lustre client itself?<div><br></div><div>-cf</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 17, 2017 at 2:52 PM, Jessica Otey <span dir="ltr"><<a href="mailto:jotey@nrao.edu" target="_blank">jotey@nrao.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Update #1. Robinhood change log consumption is also producing the
same effect against a native 2.x file system instance. So the
'legacy' aspect of our two production instances does not seem to
be a factor... <br>
</p>
<p>Update #2. Currently running, per Colin Faber's suggestion: find
/mnt/lustre -exec lfs path2fid {} \; <br>
</p>
<p>This does not (so far) provoke a disconnection.</p><span class="HOEnZb"><font color="#888888">
<p>Jessica<br>
</p></font></span><span class="">
<div class="m_-5165440964190648035moz-cite-prefix">On 5/17/17 2:04 PM, Jessica Otey wrote:<br>
</div>
<blockquote type="cite">
<p>We also have a third Lustre file system that originated as
2.4.3, and has since been upgraded to 2.5.5, against which
Robinhood is currently operating as expected. This leads me to
suppose that the issue may have to do the interaction between
Robinhood and a legacy-1.8.x-now-lustre-2.5.5 system. But I
don't know. <br>
</p>
<br>
<fieldset class="m_-5165440964190648035mimeAttachmentHeader"></fieldset>
</blockquote>
<br>
</span></div>
<br>______________________________<wbr>_________________<br>
lustre-discuss mailing list<br>
<a href="mailto:lustre-discuss@lists.lustre.org">lustre-discuss@lists.lustre.<wbr>org</a><br>
<a href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org" rel="noreferrer" target="_blank">http://lists.lustre.org/<wbr>listinfo.cgi/lustre-discuss-<wbr>lustre.org</a><br>
<br></blockquote></div><br></div>