E1 and E1WC nodes keep storage and IOPS apart from the plan. IOPS is input/output operations per second, how fast the disk can read and write. That is what lets you grow the root disk after the node is created, without changing plan. Do this once your E1 node is running low on disk space. The disk only grows. If you end up needing less, create a new node at the size you want and move your data over.
Before you begin
Section titled “Before you begin”Have the node Running or Powered off, with at least 500 MB of free disk space. The root disk also needs to be free of snapshots. Delete them first if you no longer need them; see Delete a snapshot. Wait for any plan upgrade to finish, and have the node unlocked and out of recovery mode.
Increase the storage
Section titled “Increase the storage”Open the node’s Actions menu and click Increase Root Storage. Set the new value in Storage Size (GB). The read-only IOPS (R/W) field next to it updates as you type, since E1 storage carries its own IOPS rather than a plan’s fixed amount. Confirm to apply the new size.
E1 root storage runs from 75 GB up to 2,400 GB, starting at a default of 150 GB when you create the node. Below 150 GB it increases in steps of 25 GB, and from 150 GB up in steps of 50 GB.
What you get for each size
Section titled “What you get for each size”At 150 GB, an E1 root disk carries 15,000 read and 10,000 write IOPS. Every extra GB above that adds 5 read and 5 write IOPS, so a larger disk is also a faster one.
To see how much space the root filesystem has, run df -h / inside the node. If the disk filled
up before you got here, see
Troubleshooting node performance and resources.