High read load and upload cancelled on a full system

[NodeOps]

So I just found these two

CMR 12TB drive - 100% usage

The relevant topic was linked here This one is simple, you just add: storage2.piece-scan-on-startup: false to your config.yaml and then restart your node. The file walker on restart has the primary function to see how much data is currently used by your node. Disabling it can make that numbers start going out of sync. If this step doesn’t help, I recommend enabling it again. When your HDD starts filling up it may be a good idea to run file walker again to make sure you don’t get unintended ov…

Tuning the filewalker

The commonly called filewalker process, which is the functionality that goes over all pieces of the storage node’s blob folder seeking the metadata and looking for expired pieces, is basically smashing the spinning drives every time a node is restarted (both on manual restart and/or automatic upgrade). Due to the way Storj files are stored (folders with thousands of files that are created/deleted) causes some issues on Ext4 filesystems after some months of operation. They do not only cause file…

Which seems to be in line with what I have issues with.

I have changed storage2.piece-scan-on-startup from true to false

I did something, but it didn’t fix the issue.

IOwait is down to less than 30% and util is lower than 100% but still 95%+

I can see the filewalker isn’t running now