im still need a help! !!! please

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.

The redeploy didn't resolve it. PostgreSQL is still crash-looping with the same error: FATAL: could not write to file "pg_wal/xlogtemp.30": No space left on device

The filesystem is still 434MB instead of 5GB. The resize2fs command either:

1. Didn't execute successfully
2. Executed but didn't apply to the mounted filesystem
3. The volume wasn't properly unmounted before resize

Can you verify the resize2fs command completed successfully and check the current filesystem size with df -h /var/lib/postgresql/data?

Railway team - I'm experiencing the EXACT same issue as @gchamusca, also right now.

My resource IDs:

• Project: d65c968b-51a7-4dc9-b8b7-3fc29c8bed3f (C4V laser)
• - Service (Postgres): e88d18b3-c175-4a2a-9389-83885c1ea7b0
• - Environment: 5c5142b0-71ef-4bbc-8509-afe15aec2b28
• - Volume: postgres-volume (resized from ~500MB to 100GB)

Same error: FATAL: could not write to file "pg_wal/xlogtemp.XX": No space left on device

Used Railway Agent to:

1. Remove old custom start command
2. 2. Create helper service "postgres-fs-resize" that mounted same volume - completed successfully
3. 3. Tried resize2fs via pre-deploy commands - all failed with "catatonit: failed to exec pid1: No such file or directory" (binaries not in postgres container)
4. 4. Reset Postgres to default config - still crashes

This appears to be a Railway infrastructure issue with live volume resizes not propagating the filesystem expansion. Please apply the same manual fix (resize2fs on the volume) as you did in the previous brody-solved threads. This is blocking production (7 AI bots depending on this database).

Thank you!

Similar problem for me. Volume resized to 5 GB, but stuck on 1 GB, though the railway UI reports it as 5 GB, i'm getting out of storage errors at 1 GB used. The only volume on my account.

I solved my issue by having the Railway Agent resize the volume back to 1 GB. Then I had the Agent resize to 5 GB.

The volume resize to 5 GB didn't fully apply to your database's storage. We've corrected this and redeployed your Postgres service. Your data is intact and you should now have approximately 5 GB of available disk space.