You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sites/platform/src/create-apps/troubleshoot-disks.md
+20-14Lines changed: 20 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,21 +27,27 @@ To fix the error, do one of the following:
27
27
* Increase your plan's storage limits.
28
28
This can only be done by people with the [manage plans permission](/administration/users.md#organization-permissions).
29
29
30
-
## Low disk space
30
+
## Low disk space or inode exhaustion
31
31
32
-
If you have set up [health notifications](/integrations/notifications.md),
33
-
you may receive a notification of low disk space.
32
+
[Health notifications](/integrations/notifications.md) can alert you to low disk space,
33
+
inode exhaustion (a file count limit), or both.
34
34
35
-
To solve this issue:
35
+
To help identify the cause, you can:
36
36
37
37
*[Check mount usage](/create-apps/troubleshoot-mounts.md#disk-space-issues)
38
38
*[Check your database disk space](#check-your-database-disk-space) (if applicable)
39
-
*[Increase the available disk space](#increase-available-disk-space) (if necessary)
39
+
40
+
Deleting unnecessary files such as temporary files, logs, or build artifacts can free up disk space and inodes.
41
+
If you know their origin, consider setting up automated cleanup to prevent recurrence.
42
+
43
+
If cleanup measures are insufficient, you can [increase the allocated disk space](#increase-allocated-disk-space).
40
44
41
45
### Check your database disk space
42
46
43
-
To get approximate disk usage for a database, run the command `{{% vendor/cli %}} db:size`.
44
-
This returns an estimate such as the following:
47
+
If you receive a low disk space notification, the database might be a contributing factor.
48
+
49
+
To get an estimate of current database disk usage, run `{{% vendor/cli %}} db:size`.
50
+
The estimate looks something like this:
45
51
46
52
```text
47
53
+----------------+-----------------+--------+
@@ -51,12 +57,11 @@ This returns an estimate such as the following:
51
57
+----------------+-----------------+--------+
52
58
```
53
59
54
-
Keep in mind that this estimate doesn't represent the exact real size on disk.
55
-
But if you notice that the usage percentage is high, you may need to increase the available space.
60
+
Try cleaning up unused data before [increasing the allocated disk space](#increase-allocated-disk-space).
56
61
57
-
### Increase available disk space
62
+
### Increase allocated disk space
58
63
59
-
If you find that your application or service is running out of disk space,
64
+
If you find that your application or service is running out of disk space, available inodes, or both,
60
65
you can increase the available storage.
61
66
62
67
To increase the space available for applications and services,
@@ -74,12 +79,13 @@ During the `build` hook, you may see the following error:
74
79
W: [Errno 28] No space left on device: ...
75
80
```
76
81
77
-
This is caused by the amount of disk provided to the build container before deployment.
78
-
Application images are restricted to 8 GB during build, no matter how much writable disk has been set aside for the deployed application.
82
+
This is caused by the disk limit on the build container — a temporary environment used to compile
83
+
your app before deployment. The resulting image is restricted to 8 GB, no matter how much
84
+
writable disk has been allocated for the deployed application.
79
85
80
86
Some build tools (yarn/npm) store cache for different versions of their modules.
81
87
This can cause the build cache to grow over time beyond the maximum.
82
88
Try [clearing the build cache](/development/troubleshoot.md#clear-the-build-cache) and [triggering a redeploy](/development/troubleshoot.md#force-a-redeploy).
83
89
84
-
If for some reason your application absolutely requires more than 8 GB during build,
90
+
If your application requires more than 8 GB during the build phase,
85
91
you can open a [support ticket](/learn/overview/get-support.md) to have this limit increased.
0 commit comments