From my experience - I performed this when I had mysterious issues with one of my nodes and this resolved the issue.
Following is for Windows but I guess the same apply for any OS, you will know where your folders are located. You can freely delete following folders and files, and when I say freely, it means the node will work just fine and you will not loose money, but the consequences may be the Dashboard not showing any data for a couple of hours, Filewalker full run, etc. Obviously it required stopping the storagenode first.
c:\Storj\app\
- app folder where you have your storagenode.exe: all subfolders can be deleted, as well as files: revocations.db, storagenode.log, storagenode.old.v1.117.8.exe and all storagenode.old.*.exe, storagenode-updater.log, storagenode-updater.old.exe, trust-cache.jsonc:\Storj\dtb\
- the path is defined in config.yaml asstorage2.database-dir: ...
- delete all files and subfolders, not the folder itself.d:\Storj\data\
your data folder, the path defined in config.yaml asstorage.path: ...
- delete content (not the folder itself) ofd:\Storj\data\filestatcache\
,d:\Storj\data\hashstore\
,d:\Storj\data\temp\
- there should be nothing in temp anyway.- And if you have serious need and willing to the some minor risk, you can delete content of d:\Storj\data\trash. In worst case, if you are unlucky, this may lower your Audit Score by a percent or so but if your node is screwed up and have nothing to lose…
Or from the other side - you need to keep only:
- in app folder keep: config.yaml, storagenode.exe, storagenode-updater.exe
- in database folder: nothing needed
- in data folder: keep everything in
d:\Storj\data\blobs\
, filestorage-dir-verification
, and remove content of all other folders but keep the folders themselves.