The lazy filewalkers may run days. To reduce the time to hours you may disable a lazy mode. However, it would require to restart the node and the filewalker will start over.
The reinstallation was not needed. But since databases are deleted, the stat and history were lost. The history would be received from the trusted satellites after a while, but the current stat would be wrong, including payout estimation. The storage usage should be recovered by the used-space-filewalker, it just should finish without errors and stat would be updated if you do not have errors related to the databases. The bandwidth stat wouldn’t be recovered for the current period.
If your audit score is less than 100% this is mean that your node lost some data (or access to it), it’s not related to the filewalkers, audits are conducted by satellites.
No. This information was in the database, it also exist on the satellites’ side, but it will not be resent. Just the satellite will send a Bloom Filter (roughly once a week, maybe more often recently) and the Garbage Collector will use it to move the deleted data to the trash, and 7 days later the trash-filewalker will delete it permanently.
We have an emergency protection for this case: if there is less than 5GB in the allocation/disk, the node will send a message to all satellites, that it’s full.
More like yes. But you can track its progress: