Return of used data

[Alexey]

If you have an

@support26

timed out after 1m0s while verifying writability of storage directory

this is result the node to crash (to try to save it from a disqualification, if your hardware is started to fail. The node doesn’t know, is it an intermediate issue or permanent, so it will stop to allow the Operator to decide, what they would do next).
So, you need to fix the disk or the configuration to do not fail a writeability checks.

1. Try to optimize the filesystem

@Alexey

Optimizing the filesystem includes:

1. check and fix errors on the disk
2. disable 8dot3 for NTFS: NTFS Disable 8dot3name
3. disable atime (for NTFS: [Solved] Win10 20GB Ram Usage - #17 by arrogantrabbit), for Linux - please, use the search here or in the internet
4. do a defragmentation if NTFS and enable the automatic defragmentation, if you disabled it (it’s enabled by default)
5. Disable indexing (Windows only)
6. Move databases to SSD (for Windows: Move databases on Windows storagenode - #2 by Alexey, for docker: How to move DB’s to SSD on Docker)
7. If you have a managed UPS, enable the write cache (for Windows - in the disk volume Policy, you need to select both checkboxes)
8. Add more RAM, if possible. Or add SSD cache before the disk subsystem (for Windows it’s possible too, but you need to use a tiered Storage).

2. If this wouldn’t help and you still have crashes because of a failed writeability/readability checks, then you may increase the related timeout on 30s, save the config and restart the node.

Fatal Error on my Node

No And Depending on your error. For the failed a readability check error you may increase a readable timeout, for the failed a writeability check error you may increase a writeable timeout. But it’s better to increase only on 30s first, so it would be storage2.monitor.verify-dir-readable-timeout: 1m30s storage2.monitor.verify-dir-readable-interval: 1m30s Or storage2.monitor.verify-dir-writable-timeout: 1m30s You need to save the config after the change and restart the node.

@Alexey

Just note, there are two checkers and related timeouts:

There are other changes as well. I said that this only a feature which now has a timeout on dir verification. You may increase a timeout, but please be careful - do not put more than 5 minutes, otherwise you will risk to start to fail audits. The parameter is called PS C:\Users\user> & ‘C:\Program Files\Storj\Storage Node\storagenode.exe’ setup --help | sls verify --storage2.monitor.verify-dir-readable-interval duration how frequently to verify the location and readability of the stor…

So, if you have a read timeouts, you need to increase the readable timeout and readable interval (because they are equal 1m0s by default). If you have writeability timeout, you need to increase the writable timeout as well