2 months ago
Hey!
My Postgres volume is full. I resized it from 500MB to 5GB but the filesystem was not expanded. Postgres keeps crash-looping with FATAL: could not write to file "pg_wal/xlogtemp.30": No space left on device. I need the filesystem expanded so Postgres can complete WAL recovery.
Can someone help me? I cannot lose this data :(
2 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Hey! I took a look and confirmed the issue — when you resized the volume from 500 MB to 5 GB, the underlying ZFS volume was expanded but the ext4 filesystem on top of it was not. That's why Postgres was still seeing the old 500 MB limit and crash-looping on WAL writes.
I've fixed this by:
- Removing the crashed deployment to fully unmount the volume
- Running a filesystem check (
e2fsck) — came back clean - Expanding the ext4 filesystem to match the full 5 GB (
resize2fs) - Redeploying the service
Your Postgres instance is back online and now has the full 5 GB of disk space available. You shouldn't see any data loss since the filesystem was intact, just full.
If you're approaching disk limits regularly, consider setting up data retention policies or periodic cleanup to keep usage in check. Let us know if you run into any other issues!
Status changed to Awaiting User Response Railway • 2 months ago
Status changed to Solved nico • 2 months ago
2 months ago
Thank you so much! I truly appreciate your help and the efficiency with which the adjustments were handled. Rest assured, I will keep a close eye on our storage usage to ensure this doesn't happen again. Thanks again, and have a great week!
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Solved guialmorim • 2 months ago