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?
-cf
On Wed, May 17, 2017 at 2:52 PM, Jessica Otey <jo...@nrao.edu> wrote:
> 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...
>
> Update #2. Currently running, per Colin Faber's suggestion: find
> /mnt/lustre -exec lfs path2fid {} \;
>
> This does not (so far) provoke a disconnection.
>
> Jessica
> On 5/17/17 2:04 PM, Jessica Otey wrote:
>
> 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.
>
>
>
> _______________________________________________
> lustre-discuss mailing list
> lustre-disc...@lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
robinhood-support mailing list
robinhood-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/robinhood-support
