No, the filesystem can be active.
The only important thing is to activate changelogs (i.e. register a
changelog client) before the initial scan begins
to make sure robinhood misses no entry.
Maybe I can share some experience... What kind of bug did you face? a
crash ? a hang? What Lustre / OS versions?
Regards
On 09/15/16 14:37, Wendy Poole wrote:
Is there an underlying assumption with the robinhood code that the
filesystem is quiescent(inactive) while the first initial scan is
performed ? trying to track down a bug and realized that someone was
writing to the filesystem while performing an initial scan and wanted
to eliminate possibilities.
Thanks
------------------------------------------------------------------------------
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support
------------------------------------------------------------------------------
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support
