Wrong used & remaining disk space

[Alexey]

It requires skills to find errors in the logs and post them here.
The popular ones:

@thelastspark

2024-06-18T08:06:18-04:00 ERROR pieces failed to lazywalk space used by satellite {"error": "lazyfilewalker: exit status 1", "errorVerbose": "lazyfilewalker: exit status 1\n\tstorj.io/storj/storagenode/pieces/lazyfilewalker.(*process).run:85\n\tstorj.io/storj/storagenode/pieces/lazyfilewalker.(*Supervisor).WalkAndComputeSpaceUsedBySatellite:130\n\tstorj.io/storj/storagenode/pieces.(*Store).SpaceUsedTotalAndBySatellite:707\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run:58\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:51\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}
2024-06-18T08:06:18-04:00 INFO lazyfilewalker.gc-filewalker subprocess exited with status {"satelliteID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "status": 1, "error": "exit status 1"}

It can be fixed by optimizing your disk subsystem or adding a cache (RAM and/or SSD).
The alternative is to run in with lazy mode disabled:

@Alexey

pieces.enable-lazy-filewalker: false

The other popular is

@jammerdan

2024-05-18T23:10:10Z ERROR piecestore failed to add bandwidth usage {"Process": "storagenode", "error": "bandwidthdb: database is locked"

but not only bandwidth.db, here you could find other databases are locked, this is mean that your disk subsystem cannot keep-up, and there are several solutions:

• move databases to another less loaded disk/SSD
• add cache