6 days ago
Project: bi-bling-mealtime (605219ca-a14b-45bb-861e-f5abf1f94d82)
Service: bi-bling (da8fcc42-2cbf-4e62-8c9d-0cbb1c848bf1), environment: production
Volume: vol_yxha5q58io5rgnt9
The volume is stuck at 512 MB. I attempted to grow it six times through four different mechanisms (dashboard, CLI, API); every attempt returns "applied" but the mounted volume stays at 512 MB after redeploy. My Hobby plan allows volumes up to 5 GB.
The service was hitting ENOSPC because of this (we've since reduced disk usage on our side, so it's no longer urgent), but the resize itself never takes effect. Could you check what is blocking it on your side?
1 Replies
Status changed to Awaiting Railway Response Railway • 6 days ago
6 days ago
The volume has a pending (unapplied) resize to 5120 MB, which is 120 MB over the Hobby plan's 5000 MB cap. This happens when "5 GB" is converted as 5 × 1024 instead of the SI-based 5 × 1000 that Railway uses. The platform rejects the over-cap request each time, which is why every retry through the dashboard, CLI, and API appears to succeed but never changes the volume's actual size. To fix this, discard the pending change on the production environment's deploy bar, then resize the volume to 5000 MB (or any value at or below that) and apply it.
Status changed to Awaiting User Response Railway • 6 days ago