Hi all, I noticed on my Lustre 2.14.0 cluster running Robinhood 3.1.5 that my changelogs were never reaching zero.
It appears that files that are imported from a backing archive, but are not modified or removed from the backing archive (i.e., never reach new or modified in lhsm parlance), go in a loop of the following: 1. RBH sees close associated with the import event or a subsequent open/read/close sequence. 2. RBH determines that since the file is not already in new or modified states, it must get a fresh llapi_hsm_get_state to see if it changed. This appears to occur on CLOSE event. 3. llapi_hsm_get_state does an open/ioctl/close, throwing another close on the tail of the CL queue. 4. RBH clears the just processed close from the CL, but the new one persists. 5. Rinse and repeat starting at 2. If 1M files are imported, the changelog remains at roughly 2M entries (one open and one close per file), though it's constantly being rototilled by RBH. Thoughts? ellis _______________________________________________ robinhood-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/robinhood-support
