Alexey
November 28, 2024, 4:09am
4
The usual restart with enabled scan on startup should fix the issue.
Only wait until all used-space-filewalkers will finish the scan since the last restart.
Because right now you logs shows only several starts of the used-space-filewalkers but only a few completed.
I have a suspicion that we might introduced a bug in used-space-filewalker, when we tried to implement a continuation of the used-space-filewalker.
You can test that:
Stop and remove the container (or stop the service, if you use a service based setup)
Rename the used_space_per_prefix.db database …