Disk usage discrepancy?

[kchiem]

@Alexey

yes, they usually should match, unless you have errors related to gc-filewalker, lazyfilewalker and retain in your logs.
I suspect context canceled errors (high disks load) and/or FATAL errors (the filewalker update the database only when it’s successfully finished, otherwise it will start from the beginning on each restart).

I only see about a dozen INFO lines each for gc-filewalker and lazyfilewalker in the logs, and about a dozen ‘retain’ WARN lines, something like:

WARN retain failed to delete piece {“process”: “storagenode”, “Satellite ID”: “XXX”, “Piece ID”: “YYY”, “error”: “pieces error: filestore error: file does not exist”, “errorVerbose”: “pieces error: filestore error: file does not exist\n\tstorj.io/storj/storagenode/blobstore/filestore.(*blobStore).Stat:110\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).pieceSizes:245\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).Trash:290\n\tstorj.io/storj/storagenode/pieces.(*Store).Trash:404\n\tstorj.io/storj/storagenode/retain.(*Service).trash:364\n\tstorj.io/storj/storagenode/retain.(*Service).retainPieces:341\n\tstorj.io/storj/storagenode/retain.(*Service).Run.func2:221\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}

Nothing for “context canceled”.

There were some filewalker processes running yesterday, but they’re not running now, so I’ll assume they completed. Still, the discrepancy remains.