New accounts will be limited because they didn’t read the forum and did not try to use a search at least. If you pass this simple test - your account will not be limited.
The problem is widely discussed in this thread, so I moved yours another one thread here.
There are two (three) reasons:
- You have database related errors in your logs
- You have filewalker related errors in your logs
- You have both
Solution depends on what’s kind of error did you meet. If it’s a malformed, not a database, then you need to use these articles:
- https://support.storj.io/hc/en-us/articles/360029309111-How-to-fix-a-database-disk-image-is-malformed
- https://support.storj.io/hc/en-us/articles/4403032417044-How-to-fix-database-file-is-not-a-database-error
Both can be solved with the late article, but with a downside: the current stat and history will be lost. However, it wouldn’t affect the reputation and/or payout.
The second type of errors, related to a filewalker, can be solved by optimizing the filesystem, or by disabling a lazy mode.
The first is preferred, of course, however, the second one is an ultimate solution. In expense of the lost races of course.
Optimizing the filesystem includes:
- check and fix errors on the disk
- disable 8dot3 for NTFS: NTFS Disable 8dot3name
- disable atime (for NTFS: [Solved] Win10 20GB Ram Usage - #17 by arrogantrabbit), for Linux - please, use the search here or in the internet
- do a defragmentation if NTFS and enable the automatic defragmentation, if you disabled it (it’s enabled by default)
- Disable indexing (Windows only)
- 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)
- If you have a managed UPS, enable the write cache (for Windows - in the disk volume Policy, you need to select both checkboxes)
- 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).