Troubleshoot disks

For more general information, see how to troubleshoot development.

Exceeding plan storage limit

Professional plans come with a default amount of storage that you can change with your plan. The storage is allocated among your services and applications using the disk parameter in their configuration files.

You might accidentally set the sum of all disk parameters in the files to exceed your plans storage limit. For example, by setting disk: 4096 for a MySQL service in .platform/services.yaml and disk: 4096 in .platform.app.yaml for a plan with a 5 GB storage limit.

In such cases, you get an error like the following:

Error: Resources exceeding plan limit; disk: 8192.00MB > 5120.00MB; try removing a service, or add more storage to your plan

To fix the error, do one of the following:

• Lower the disk parameters to a value within your plan’s storage limits. Note the limits to downsizing disks.
• Increase your plan’s storage limits. This can only be done by people with the manage plans permission.

Low disk space

If you have set up health notifications, you may receive a notification of low disk space.

To solve this issue:

• Check mount usage
• Check your database disk space (if applicable)
• Increase the available disk space (if necessary)

Check your database disk space

To get approximate disk usage for a database, run the command platform db:size. This returns an estimate such as the following:

+----------------+-----------------+--------+
| Allocated disk | Estimated usage | % used |
+----------------+-----------------+--------+
| 1.0 GiB        | 520.3 MiB       | ~ 51%  |
+----------------+-----------------+--------+

Keep in mind that this estimate doesn’t represent the exact real size on disk. But if you notice that the usage percentage is high, you may need to increase the available space.

Increase available disk space

If you find that your application or service is running out of disk space, you can increase the available storage.

To increase the space available for applications and services, use the disk keys in your .platform.app.yaml and .platform/services.yaml files. The sum of all disk keys can’t exceed the available storage in your plan.

If you need more storage to fit the sum of all disk keys, increase your plan’s storage limits. This can only be done by people with the manage plans permission.

No space left on device

During the build hook, you may see the following error:

W: [Errno 28] No space left on device: ...

This is caused by the amount of disk provided to the build container before deployment. Application images are restricted to 8 GB during build, no matter how much writable disk has been set aside for the deployed application.

Some build tools (yarn/npm) store cache for different versions of their modules. This can cause the build cache to grow over time beyond the maximum. Try clearing the build cache and triggering a redeploy.

If for some reason your application absolutely requires more than 8 GB during build, you can open a support ticket to have this limit increased.