a month ago
PostgreSQL service crash-looping with 'No space left on device' error on pg_wal/xlogtemp.33. Resized volume from 500MB to 5GB via Live resize but the container still sees no space after restart. Database stuck in crash loop, cannot accept connections. Need the volume resize to take effect or the WAL files cleared so Postgres can complete recovery.
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Still happening after redeploy. New container, same error. Volume mount path changed to vol_164nwfl146dlq3wv but still showing no space. The UI shows 5GB allocated but the container filesystem is not seeing the expanded space. Need Railway team to manually expand the filesystem on the backend as described in the solved thread.
a month ago
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.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved Anonymous • about 1 month ago