hi,
one of my nodes got DQ on one satellite - since it was my main income (2tb) i want to start a new one.
can i safely delete the blob folder of the satellite that has DQ me or do i have to wait until some GC deletes the useless files ?
fyi i know the reason of the DQ i dont need support on this.
Hi, It’s not fully clear what is your plan.
As of now, storagnodes are connecting to 4 satellites by default (us1,eu1,ap1,saltlake).
Let’s say one of your satellite (eg. eu1) DQd your node. You have two options:
Start over from the beginning: this requires full identity generation, everything from the beginning.
Keep the storagenode running with restricted set of satellite (eg. us1,ap1,saltlake). And may or may not starting a new one. → It’s better if you have data for other satellites…
For 2, you need two things:
storage2.trust.sources configuration variable to the coma separated list of remaining satellite IDs, can be chosen from here: https://www.storj.io/dcs-satellites)can i safely delete the blob folder…
This is actually the same as the last point, without removing the database entries → you will see a lot of strange errors in the log files. But don’t expect any other problem…
nr 3
Gracefull exit and then step one.
with the right satelite id could be handy. force deletion with no errors.
my plan is to free up space to move some trashdata to the hdd thats dieing (or had filesystem problems)
then start new node on freed hdd thats fine
so my node has been dq from eu1 - and the blob folder v4kw… is still 1,8TB - >
GE will take time and i wont loose the data from the other satellites that still are fine with my fckt node
You can safely delete the blobs folder for the satellite which disqualified your node. Just make sure it’s the right one.
To help with 
please read 
The GE would help to exit only from remained satellites.
@4ich
But this one can be deleted with the forget-satellite command for that satellite. Do not forget to use --force flag, to also remove data.