Disk usage discrepancy?

[nyancodex]

All I can say is good luck bro

Disk usage discrepancy?

Hey @Alexey, This is not the same. I found this thread as well, but this thread was about a difference between the Disk usage shown on the dashboard, between the left (Average) and the right window (Total). At list on the initial level. My problem is completely different and we are talking about a huge difference. According to the dashboard a total of 8.27 TB (Used) + 3.86 TB (Trash) = 12.13 TB should be consumed. As you can see from the next screenshot, the amount of storage consumed in blobs…

[Alexey]

Hi, the suggestion is the same

Disk usage discrepancy?

The scan on startup is enabled by default. So, if you disabled it, you already know how to enable it back This is a command line option: --storage2.piece-scan-on-startup if set to true, all pieces disk usage is recalculated on startup (default true) or as a parameter storage2.piece-scan-on-startup: true in your config.yaml. If you changed it, you need to save the config (or stop and remove the container in case of docker) and restart the node (or…

[humbfig]

Node dashboard still reporting larger than real used space.
So, will this ever be solved?

df -T --si
/dev/mapper/cachedev_2 ext4 8.6T 5.4T 3.3T 63% /volume8

[Alexey]

Hello @humbfig,
Welcome back!

Please enable scan on startup, if you disabled it (it’s enabled by default), save the config and restart the node.
Wait until all used-space-filewalkers will finish the scan for each trusted satellites without any errors related either to a filewalker or databases. This may take several days.

[humbfig]

Hi Alexey!

I was sure I had the scan enabled, but it wasn’t…
Anyway, it’s been like that for a few months, and I have seen “scan compatible” activity in this disk a few times since. Also, I recall having read somewhere in the forum that a certain new version would force the scan somewhen…
Doesn’t matter… right now it is scanning for sure. I will report the result once finished.

I have another node (that I can not access in this moment) with 600GB in the trash that will not vanish (also for a few months). Any thoughts on that one?

[EasyRhino]

the activity spikes could be from garbage collection btw, since the used space filewalker usually starts only at the beginning of the node and then never again until a restart.

[humbfig]

yep, you’re probably right… in a week (I estimate) I’ll know for sure…

[Alexey]

@humbfig

I have another node (that I can not access in this moment) with 600GB in the trash that will not vanish (also for a few months). Any thoughts on that one?

This node requires to run the scan on startup at least once. The scan will correct all discrepancies - in used space, in free space, and in space occupied by the trash.
If your trash really takes up 600 GB, then you need to check which folders took up most of the space, perhaps you have data left from decommissioned satellites. In that case you need to use this guide: How To Forget Untrusted Satellites with a --force flag.

[humbfig]

As for the node with too much legacy trash, I will try the same when I regain access.
thanks!

[Alexey]

It’s not too much

[LxdrJ]

Yesterday the node did a restart, I was wondering that I lost a couple of GBs. But something is still there

Saved the logs but dont show any result with this command

docker logs storagenode 2>&1 | grep error | grep -E “filewalker|database” | tail

Somehow the blobs are quite big

19G /mnt/storj/storage/blobs/qstuylguhrn2ozjv4h2c6xpxykd622gtgurhql2k7k75wqaaaaaa
132M /mnt/storj/storage/blobs/pmw6tvzmf2jv6giyybmmvl4o2ahqlaldsaeha4yx74n5aaaaaaaa
64G /mnt/storj/storage/blobs/v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa
365G /mnt/storj/storage/blobs/ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa
446G /mnt/storj/storage/blobs

[Alexey]

Did you enable the scan on startup before restart the node?
You may track the filewalker with these scripts:

Storagenode.exe stopping for too long, for 10h+

Windows/PowerShell Logs should be at least info level Used space filewalker Regulated by the parameter in the config.yaml file or as a command line argument (add -- before the parameter, remove :, place it after the image name in your docker run command): # if set to true, all pieces disk usage is recalculated on startup (default true) storage2.piece-scan-on-startup: true to watch for a progress: cat "C:\Program Files\Storj\Storage Node\*.log" -Wait | sls "used-space-filewalker" | sls "sta…

[LxdrJ]

I guess scan on startup should be on, I have standard Docker conf.

I was scrolling the logs a bit there was an update, the filewalkers were runing several times yesterday. Today I did a full shutdown of the system suddenly there was more space used

[Alexey]

Do not use a scroll , use scripts:

Storagenode.exe stopping for too long, for 10h+

Windows/PowerShell Logs should be at least info level Used space filewalker Regulated by the parameter in the config.yaml file or as a command line argument (add -- before the parameter, remove :, place it after the image name in your docker run command): # if set to true, all pieces disk usage is recalculated on startup (default true) storage2.piece-scan-on-startup: true to watch for a progress: cat "C:\Program Files\Storj\Storage Node\*.log" -Wait | sls "used-space-filewalker" | sls "sta…