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.
And it’s been on aa since I restarted the node. About 30 minutes now.
It’s even slower than the lazy version.
Utterly doomed.
EDIT: Couple hours later, it’s on ag. Down to 611g free space on the disk.
So so doomed.
EDIT 2: So just as a test, I shut down my other process, to see if this non-lazy walker would get any faster. Nope, at least not in any perceptible way. Stuck on “am” for at least 15 minutes since I did that. I seriously think the lazy was faster.
Doom, doom doom doom, doooooom.