Trash not existing

pangolin · March 28, 2024, 2:39pm

One of my nodes is showing like 2 TB of trash but this trash does not exist. There are only empty folders in the trash folder. Restarts and waiting some days did not help. Any Idea how to solve this problem?

zip · March 28, 2024, 2:58pm

Change config option storage2.piece-scan-on-startup: false to true and restart the node. Then you can change it back.
It might take hours or even days to scan everything, depending on how fast the drive/filesystem is and how big the node is.
Once all will be scanned, the metrics should update and ~match what is actually on the drive.

pangolin · March 28, 2024, 3:13pm

This option doesn’t exist in my config.yaml. Maybe because the node is very old?

I will add it now and seee what happens…

zip · March 28, 2024, 3:36pm

Yes, it might have been added in more recent versions. I think however if it is missing it is enabled by default.
You should be able to tell by the disk utilisation. If startup scan is enabled then the drive will be quite utilised after the node restart and until it will complete the scan.

Alexey · March 29, 2024, 8:09am

You need to check your logs for errors, related to a filewalkers (search for walk|retain|trash and failed|error|ERROR, also for FATAL errors).
If you have any - you likely need to figure out, why your disk is so slow.
As a last resort you may disable a lazy mode:

Huge drop of Average disk space used

Please try to disable lazy filewalker, it will turn on the normal (with a normal priority):
# run garbage collection and used-space calculation filewalkers
# as a separate subprocess with lower IO priority (default true)
pieces.enable-lazy-filewalker: false
save the config and restart the node. If you use docker, you may provide this flag after the image name: --pieces.enable-lazy-filewalker=false