Filewalker failed

Node Operators troubleshooting
1

I recently enabled the space-filewalker after the node automatically updated to 109.2. And I found that the filewalker failed. Not sure how can I resolve that?

There are some post mentioned that can disable ‘lazy’ mode but I am not sure where I can disable it.

both the startup scan and lazy filewalker are set as true in the config.
- --storage2.piece-scan-on-startup true
- --pieces.enable-lazy-filewalker true

2024-07-31T09:07:01Z ERROR pieces used-space-filewalker failed {"Process": "storagenode", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Lazy File Walker": false, "error": "filewalker: context canceled", "errorVerbose": "filewalker: context canceled\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkSatellitePieces:74\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatellite:79\n\tstorj.io/storj/storagenode/pieces.(*Store).SpaceUsedTotalAndBySatellite:721\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}

2

I have the same issue with the same version :confused:

3

If you run your node on Windows, then it seems to be a known issue:

You need to disable the lazy mode.

4

It is on Debian. Btw, how to disable lazy mode?

5

Change this:
pieces.enable-lazy-filewalker true

to this:
pieces.enable-lazy-filewalker false

6

I thought that if I turn this to False, then no filewalker would be run

7

No, there is an other option, you can controll the used space file walker at startup with these:

storage2.piece-scan-on-startup true - when your node starts, used space file walker will start as well

or

storage2.piece-scan-on-startup false - when your node starts, used space file walker will NOT start

For the lazy filewalker:

pieces.enable-lazy-filewalker false - normal filewalker will be used

or

pieces.enable-lazy-filewalker true - lazy filewalker will be used

1 Like
8

In the linked thread the failed filewalker is a consequence of a “slow shutdown”, which is usually happen because of an Unrecoverable and/or FATAL error or the shutdown request somewhere earlier.
In the linked case it’s

Something is stopped their node.