So, how to debug failing filewalkers with "context canceled"

okay I searched for used-space-filewalker and looked at the first couple pages of results to see if there were logs. I know, highly scientific statistical sampling.

4 people had context canceled errors:

Disk usage discrepancy? - Node Operators / troubleshooting - Storj Community Forum (official)

HDD failing, filewalker / bloom filter issue? What am I looking at? - Node Operators / troubleshooting - Storj Community Forum (official)

POWER outage = 3 nodes not coming back online - Node Operators / troubleshooting - Storj Community Forum (official)

Storj restart always - Node Operators / troubleshooting - Storj Community Forum (official)

Filewalker crashes node - Node Operators / troubleshooting - Storj Community Forum (official)

One guys had context canceled error but there were… a lot… of other problems simultaneously:

Node crashes after restart - Node Operators / troubleshooting - Storj Community Forum (official)

One guy had a context canceled error, but the cause was definitely not performance but the storage-dir-verification.

POWER outage = 3 nodes not coming back online - Node Operators / troubleshooting - Storj Community Forum (official)

I didn’t see any log fragments for used-space-filwalker that didn’t say context canceled, which may be part of the problem with the error message… it’ gets used for possibly lots of different underlying problems.