Please, elaborate, how the storagenode can figure out, that the data folder is missing?
The database was on the missed data folder too, as a config file…
When the data folder disappear, the storagenode failed and restarted by the docker.
Now it doesn’t see either its config file or the database.
From the storagenode’s point of view - it’s a clean setup with an empty folder (mountpoint) and it’s started from scratch…
The suspension mode is a good suggestion from the SNO point of view, but a very bad from the satellites’ and customers’ points of view:
- your node doesn’t have requested files, but they can be requested by customers and they got an error “file not found”;
- it can trigger the repair job, because all pieces on your node will be marked as temporary unhealthy;
- if the repair job has been triggered, the payment for repairing would be taken from the satellite’s operator pocket, not from the held amount of the suspended node;
- the suspended node will lose the repaired pieces, because they will be stored on more reliable nodes;
- the satellite operator will pay for inaccessible data from its pocket until you fix the problem or until a week is gone.
The current implementation of suspension will be used only if your node would answer with unknown error. It’s not so great number of nodes as if were taken into account the “no such file” errors.