My very old node is about to finally fill 6TB! Good milestone accomplished! With the easier mgmt of a <8TB node to move around, I’ll be starting up a new node soon.
Be sure not to over-allocate space! Allow at least 10% extra for overhead. If you over-allocate space, you may corrupt your database when the system attempts to store pieces when no more physical space is actually available on your drive.
This request seems more of a hasty un-optimized estimate to keep the nodes safe. Which i do not blame one bit, but i feel this recommendation can be discussed for the network’s health.
100x 10TB nodes = 100TB returned to the network. That seems like a very realistic scenario currently.
Based on the fact that my DB files are 1.5GB, I don’t see the benefit of having nearly 1TB of excess space.
Is there also excess space needed for un-calculated “deleted” files in temp?
Notes that i added to the idea above with seperating the DB path from the Storage files:
1) The requirement to reserve 10% overhead on the storage drive can be removed. a) On an 10TB total node, you're asking for 1TB of storage for the database overhead. This seems a little bit over the top, and would return this storage to be available to the network. Alternative: Ask for a recommended realistic reservation. 100GB? 2) as mentioned previously, performance for both the Node and the StorJ network would improve by removing IOPS demand to the storage drive. Also resulting in less repair traffic due to nodes failing faster from the high IOPS demand on the storage volume.