<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body 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>
<p>Jessica<br>
</p>
<div class="moz-cite-prefix">On 5/17/17 2:04 PM, Jessica Otey wrote:<br>
</div>
<blockquote cite="mid:32c23887-3ee5-c0be-8df5-8b9d6a6791f1@nrao.edu"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<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="mimeAttachmentHeader"></fieldset>
</blockquote>
<br>
</body>
</html>