ERROR piecestore:cache error getting current space used calculation: {"error": "context canceled"}

Node Operators troubleshooting
1

The node works for a while than it exits with

2020-02-16T20:12:02.387Z        ERROR   nodestats:cache Get disk space usage query failed       {"error": "context canceled"}
2020-02-16T20:12:02.396Z        ERROR   piecestore:cache        error getting current space used calculation:   {"error": "context canceled"}
2020-02-16T20:12:04.526Z        ERROR   piecestore:cache        error during init space usage db:       {"error": "piece space used error: context canceled", "errorVerbose": "piece space used error: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*pieceSpaceUsedDB).Init:72\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run:67\n\tstorj.io/storj/storagenode.(*Peer).Run.func6:512\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-02-16T20:12:04.526Z        ERROR   piecestore:cache        error persisting cache totals to the database:  {"error": "piece space used error: context canceled", "errorVerbose": "piece space used error: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*pieceSpaceUsedDB).UpdatePieceTotals:174\n\tstorj.io/storj/storagenode/pieces.(*CacheService).PersistCacheTotals:90\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:76\n\tstorj.io/common/sync2.(*Cycle).Run:87\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run:71\n\tstorj.io/storj/storagenode.(*Peer).Run.func6:512\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}

Seems that it tries to store some data in a corrupt table after some working.

best regards
Michael

2

No, it’s too busy with calculations. How is your disk connected? Why is it so slow?
Do you use the extended mount with type ‘bind’ in your docker-compose.yaml or just simple volume?
If the simple syntax, then it’s equivalent of very dangerous -v option in the docker run command

Because now your node is deal with a piece_spaced_used.db database.
Looks like you hardly damaged or modified it

3

Currently it´s a bind mount with a NFS storage. Starting next month the whole setup will be migrated to a dedicated system with local HDD. So hopefully after the migration everything runs smooth. But anyways i´m totally happy for your help and that the node is back online.

best rgeards
Michael

4

It will not work normally with NFS or SMB. Only local connected. Or at least iSCSI, but it’s a dangerous setup anyway.
With one lost network packet you could lose a piece.

5

If the node get´s free prop. i can start earlier the migration

6

At the moment I can suggest only to restart it and hope that it’s survive