All, I have been observing for a while now a difference between how full robinhood believes our filesystem is and how full lfs df -h reports it is.
I am wondering if anyone has any insight into this. A bit of history... I run frequent reports against the robinhood database, which also include the output of the lfs df -h command. Historically, the total based on rbh-du and lfs df were essentially identical. Lately, they seem to keep growing apart--what seems to bring them back together is doing a full scan of the file system. As time passes after a scan (changelogs are on), the 'lfs df' command reports that usage is more and more full than rbh-du says it is. Indeed, I recently reinstalled (upgraded) my robinhood and noticed that when the report ran precisely after the filescan and before the service was activated (so no changelogs were being consumed) the difference was precisely zero. I believe that is a clue... but I don't know why this is happening (when there was a lengthy period where it wasn't happening) or what to do to fix it. Also, it might help to know that there is a non-negligible amount of moving files from one OST to another taking place. Thanks, Jessica -- Jessica Otey System Administrator II North American ALMA Science Center (NAASC) National Radio Astronomy Observatory (NRAO) Charlottesville, Virginia (USA) ------------------------------------------------------------------------------ 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
