On 03/28/17 19:54, Ron Kerry wrote: > When robinhood (2.5) is configured to process changelogs, is it still a > best practice to perform a periodic full filesystem scan. Yes because not all changes in the filesystem do trigger a changelog, and some attributes are updated a "lazy" way in Lustre (like st_blocks) so robinhood can't get their value immediatly. > If so, what is the best way to accomplish that scan? Is it just running a > "rbh-lhsm -S > --once" command? Yes, or (as you wish) you can also run it regularly as a daemon (without --once option). In this case the scanning interval is the one specified in the documentation.
> Does it requires regular robinhood (processing changelogs) to be down? No, they can be done simultaneously. > Does it require a quiet Lustre filesystem? Not necessarily, but the scan could take longer if the filesystem is under a heavy load. > Do these answers change for Robinhood v3? With robinhood v3, you can define a custom update policy to automatically refresh entry attributes. This reduces/eliminates the need for scanning. See this thread for more info: https://sourceforge.net/p/robinhood/mailman/message/35638719/ Thomas. ------------------------------------------------------------------------------ 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
