Volume filesystem not expanded after resize — stuck at 434MB despite 5GB allocation
hoskhatibi
HOBBYOP

2 months ago

My PostgreSQL volume was resized from 500MB to 5000MB. The Railway API confirms the change (sizeMB: 5000), and the underlying block device shows

~4.66 GB in /proc/partitions. However, the ext4 filesystem was never expanded:

df -h shows: 434M total, only 89MB free

This originally caused a PostgreSQL crash-recovery loop — WAL redo would complete but the checkpoint write failed with "No space left on device."

I recovered by running pg_resetwal from a temporary Alpine service, but the filesystem is still 434MB.

I attempted resize2fs and the EXT4_IOC_RESIZE_FS ioctl from inside containers, but both fail with "Operation not permitted" due to missing Linux

capabilities.

Request: Please run resize2fs (or equivalent) on the host to expand the ext4 filesystem to fill the 5GB block device. ext4 supports online growth,

so no downtime should be needed.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 2 months ago


2 months ago

Hey, your volume resize from 500MB to 5GB didn't fully apply on our end. We've fixed it and redeployed your service. You should now see the full 5GB available.


Status changed to Awaiting User Response Railway 2 months ago


Status changed to Solved brody 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...