You are correct - all filewalkers should finish their job, only then the info will be updated in the local databases. The dashboard took this information from the local databases.
If the node is restarted before these filewalkers are finished, it will start over from the beginning. Databases are updated only after the successfully finished scan.
There are at least three filewalkers for each satellite:
- used space filewalker (
used-space-filewalker) - updates used space in the databases - garbage collector filewalker (
gc-filewalker) - collect the garbage (deleted pieces) - retain filewalker (
retain) - moves the garbage to the trash collector- removes expired pieces (if the customer specified the expiration date for the piece)piece:trash- cleans the trash
If your disk subsystem is slow (virtualized, USB, network filesystem, etc.), these filewalkers may works days. If the disk is slow to respond, the node may stop itself, if the write or read check would fail because of timeout.