Relationship between Lazy Filewalker and piece-scan-on-startup, explanations of settings

[jammerdan]

@ad329

However it still doesn’t answer my question of what “piece-scan-on-startup” is for, and why would i want to turn that on?

It does:

Calculates disk usage by scanning all pieces and updates the local node databases afterwards with these values

Normally the node should track every upload and deletion sizes and update the nodes databases accordingly. But this does not always work without issues as the database can become corrupted or locked while it wants to update a value. So a full scan is required from time to time have that corrected. This setting enables or disables this scan on every startup.

@ad329

Also, why doesn’t badger cache work with lazy filewalker.

Badger cache: are we ready?

Because it needs the cache exclusively. The lazy filewalker spawns a new process and there is no guarantee that only one is active. A TTL cleanup would spawn while garbage collection is active and that’s game over for the badger cache.