After disabling lazy mode the filewalkers didn't print anything to the logs

[Alexey]

You may see it right now:

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

Solution for Linux: When you redirect your dbs you can use the foldername to insert some Unique ID to the node. This ID will appear in the output of ‘ps’ for --info & --info2 parameters. ps -ef | grep ‘used-space-filewalker’ | grep ‘/app/’ | grep ‘nodeid’ Output of ps: root 11556 10062 7 10:04 ? 00:44:25 /app/storagenode used-space-filewalker --storage config/storage --info dbs-nodeid/piecestore.db --info2 dbs-nodeid/info.db --pieces config/storage --driver --filestore.write-buffer-…

Even for a non-lazy one:

@Qwinn

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 seem it’s still working on aa.