# Debugging space usage discrepancies

**URL:** <https://forum.storj.io/t/debugging-space-usage-discrepancies/24874>\
**Category:** Node Operators\
**Created:** [January 8, 2024, 3:51pm UTC](https://forum.storj.io/t/debugging-space-usage-discrepancies/24874 "2024-01-08T15:51:06Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![elek](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/elek/32/9189_2.png) [@elek](https://forum.storj.io/u/elek)\
**Post date:** [January 9, 2024, 9:55am UTC](https://forum.storj.io/t/debugging-space-usage-discrepancies/24874/3 "2024-01-09T09:55:51Z")

</div>

> [@raert](#):
>
> For me this is 0… always.

Looks to be a bug, `garbage_collection_pieces_count` and `garbage_collection_pieces_skipped` are swapped when lazy file walker is used (default).

This should fix the problem:

[https://review.dev.storj.io/c/storj/storj/+/12076](https://review.dev.storj.io/c/storj/storj/+/12076)

Until that, you can check the value of `..._skipped`

Not: it’s still not very useful metrics, as the value is updated after any execution. If two satellites have totally different values, the first one may not be visible, only by max/min fields.

I am considering to add the satellite as tags to all of these metrics…

---

_[View the full topic](https://forum.storj.io/t/debugging-space-usage-discrepancies/24874)._