Postgres crash loop - Live Resize didn't expand filesystem (same issue as ticket from "gil4business-commits" 6h ago)
per1gyom
HOBBYOP

a month ago

Hi Railway team, I'm hitting the exact same bug that "gil4business-commits" reported 6 hours ago (resolved by brody) — Postgres crash-looping after Live Resize, with: "FATAL: could not write to file pg_wal/xlogtemp.33: No space left on device" My volume was at 1GB, I resized to 5GB via Live Resize (beta). Dashboard shows 5.00 GB but the filesystem inside the container is still at original size. WAL recovery fails at position 0/52F12158 every attempt. Project: invigorating-wholeness / production Service: Postgres Volume: postgres-volume (vol_jr6cf1g4csot8mv5) Can you please apply the same fix brody did on the previous ticket (expand the filesystem layer + redeploy Postgres)? This is blocking my production app at app.raya-ia.fr. Thanks!

Solved

2 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


a month ago

Hey, fixed this for you. The volume resize didn't fully apply to the filesystem layer, so I expanded it manually and redeployed Postgres. You should now see the full 5 GB available.


Status changed to Awaiting User Response Railway about 1 month ago


per1gyom
HOBBYOP

a month ago

Thank You


Status changed to Awaiting Railway Response Railway about 1 month ago


Status changed to Solved Railway about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...