a month ago
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/b26a3dd2-5708-4a86-
2026-04-13 10:54:08.791 UTC [33] LOG: redo done at 0/82FE30 system usage: CPU: user: 0.75 s, system: 0.34 s, elapsed: 6.98 s
2026-04-13 10:54:08.811 UTC [33] FATAL: could not write to file "pg_wal/xlogtemp.33": No space left on device
2026-04-13 10:54:08.818 UTC [7] LOG: startup process (PID 33) exited with exit code 1
2026-04-13 10:54:08.818 UTC [7] LOG: terminating any other active server processes
2026-04-13 10:54:08.820 UTC [7] LOG: shutting down due to startup process failure
2026-04-13 10:54:08.837 UTC [7] LOG: database system is shut down
5 Replies
angelo-railway
Hey, we've fixed this. The volume resize to 5GB didn't fully apply to the disk — it was stuck at 500MB. We've expanded the filesystem and redeployed your Postgres service. It should be coming back up now with the full 5GB available and your data intact.
a month ago
i have the same issue?
a month ago
working. delete thread
a month ago
Glad it's working now, we'll get this thread closed out.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Glad it's working now, we'll get this thread closed out.
a month ago
nope still broken. same issue.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hi aaaabbaaaa, your Postgres service is currently showing as online in our system and running on a 10 GB volume, so it looks like you were able to work around this. If you'd still like us to expand any of your volumes to the size you originally requested, let us know which one and we'll take care of it.
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 • about 1 month ago