# Corrupt node after power outage

**URL:** <https://forum.storj.io/t/corrupt-node-after-power-outage/27722>\
**Category:** troubleshooting\
**Tags:** docker, database, corrupted-filesystem\
**Created:** [September 2, 2024, 6:31pm UTC](https://forum.storj.io/t/corrupt-node-after-power-outage/27722 "2024-09-02T18:31:19Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [September 5, 2024, 5:42am UTC](https://forum.storj.io/t/corrupt-node-after-power-outage/27722/12 "2024-09-05T05:42:40Z")

</div>

> [@Pascal51882](#):
>
> Now that all DBs are new, I wonder if the dashboard will update the real used memory again over time?

Yes, when the used-space-filewalker would finish the scan without errors.

> [@Pascal51882](#):
>
> `satPiecesContentSize < 0`

> [@ERROR blobscache satPiecesTotal \< 0 satPiecesContentSize \< 0](https://forum.storj.io/t/error-blobscache-satpiecestotal-0-satpiecescontentsize-0/12051):
>
> My oldest node moved 20GB to the trash and at the same time logged around 10k of these errors: 2021-02-28T18:34:55.456Z ERROR blobscache satPiecesTotal \< 0 {"satPiecesTotal": -1792} 2021-02-28T18:34:55.456Z ERROR blobscache satPiecesContentSize \< 0 {"satPiecesContentSize": -1280} They don’t appear now anymore but should I be worried about those? After all, they are classified as errors, even though their message isn’t very helpful to me.

> [@ERROR blobscache satPiecesTotal \< 0](https://forum.storj.io/t/error-blobscache-satpiecestotal-0/25926):
>
> Never seen such errors before. What does it mean? 2024-04-22T18:48:37+02:00 ERROR blobscache satPiecesTotal \< 0 {"satPiecesTotal": -3072} 2024-04-22T18:48:37+02:00 ERROR blobscache satPiecesContentSize \< 0 {"satPiecesContentSize": -2560} 2024-04-22T18:48:37+02:00 ERROR blobscache satPiecesTotal \< 0 {"satPiecesTotal": -1280} 2024-04-22T18:48:37+02:00 ERROR blobscache satPiecesContentSize \< 0 {"satPiecesContentSize": -768…

So, not new, and the solution is the same - you need to have all used-space-filewalker finished without errors.  
You may track them:

```auto
docker logs storagenode 2>&1 | grep "\sused-space" | grep -E "started|completed"

```

---

_[View the full topic](https://forum.storj.io/t/corrupt-node-after-power-outage/27722)._