Disk usage discrepancy?

[Alexey]

If you did all optimizations for the filesystem mentioned before, and you still have failed the lazy filewalker, then the only thing is to disable a lazy mode

Trash not existing

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:

Save the config and restart the node. After that the progress you can track only by using a debug port

ERROR filewalker failed to get progress from database

It’s started, but it has not the extensive logging as a lazy one: So you may track it by the load of the disk or using a debug endpoint: Guide to debug my storage node, uplink, s3 gateway, satellite.

or this trick:

ERROR lazyfilewalker.gc-filewalker.subprocess failed to save progress in the database

So looking for non-lazy filewalker progress, I grepped an ls -l /proc/STORJPROCESSID/fd, using the main process ID. I found only two lines with “blobs” that seemed to match what I look for in the lazy version. lr-x------ 1 qwinn qwinn 64 Jun 15 02:29 67 -> /app/config/storage/blobs/pmw6tvzmf2jv6giyybmmvl4o2ahqlaldsaeha4yx74n5aaaaaaaa lr-x------ 1 qwinn qwinn 64 Jun 15 02:29 68 -> /app/config/storage/blobs/pmw6tvzmf2jv6giyybmmvl4o2ahqlaldsaeha4yx74n5aaaaaaaa/aa So. According to this, it would…