Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.upsun.com/llms.txt

Use this file to discover all available pages before exploring further.

For more general information, see how to troubleshoot development.

​
Low disk space or inode exhaustion

Health notifications can alert you to low disk space, inode exhaustion (a file count limit), or both. To help identify the cause, you can: Deleting unnecessary files such as temporary files, logs, or build artifacts can free up disk space and inodes. If you know their origin, consider setting up automated cleanup to prevent recurrence. If cleanup measures are insufficient, you can increase the allocated disk space.

​
Check your database disk space

If you receive a low disk space notification, the database might be a contributing factor. To get an estimate of current database disk usage, run upsun db:size. The estimate looks something like this: 
+----------------+-----------------+--------+
| Allocated disk | Estimated usage | % used |
+----------------+-----------------+--------+
| 1.0 GiB        | 520.3 MiB       | ~ 51%  |
+----------------+-----------------+--------+
Try cleaning up unused data before increasing the allocated disk space

​
Increase allocated disk space

If you find that your application or service is running out of disk space, available inodes, or both, you can increase the allocated disk space by using the upsun resources:set command. For more information, see how to manage resources. Changing container sizes will trigger a deployment on the chosen environment and affect your monthly project cost. For pricing details, see the Upsun Pricing page.

​
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 disk limit on the build container — a temporary environment used to compile your app before deployment. The resulting image is restricted to 8 GB, no matter how much writable disk has been allocated 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 your application requires more than 8 GB during the build phase, you can open a support ticket to have this limit increased.
Last modified on April 30, 2026