a month ago
My PostgreSQL service (project: zestful-radiance, volume: vol_guusxehgpttcuu9m) is stuck in a crash loop with error:
FATAL: could not write to file "pg_wal/xlogtemp.30": No space left on device
Volume was originally 500MB and filled up. I resized it to 5GB and then 10GB via the dashboard, and also tried Live Resize (beta). The Railway UI shows 497MB/5000MB used, but the container filesystem still reports no space.
I found a solved thread with the exact same issue (postgre-sql-crash-loop-after-disk-full-82a101ad) where Railway employee angelo-railway manually expanded the filesystem on the backend.
Could you please do the same for my volume? The data is critical - production database with company and customer records. Project: zestful-radiance, service: Postgres.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hi contact715,
Taking a look now — it seems you were able to recover on your end. Your Postgres service is up and running with ~1.2 GB of data on a new 10 GB volume, and mosco-api is online and healthy. Nice work getting back online.
The original volume that filled up (postgres-volume) is still sitting in your project as a detached volume — it's no longer attached to any service. Let me know if there's anything else you'd like help with here.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 27 days ago