Volume resized to 5GB but filesystem stuck at 500MB — resize fails
pierredotsol
HOBBYOP

2 months ago

I resized my volume from 500MB to 5GB in the dashboard, but the ext4 filesystem inside the container is still 433MB. The block device shows as /dev/zd384 but resize2fs fails with "open: No such file or directory while opening /dev/zd384". This caused my n8n SQLite database to corrupt when the 433MB filesystem filled up. From my deploy logs: - Volume shows 5GB in Railway dashboard - df -h inside container: /dev/zd384 433.3M - resize2fs /dev/zd384: "open: No such file or directory" - Database corrupted due to SQLITE_FULL → SQLITE_CORRUPT Is there a way to expand the filesystem to match the 5GB block device? Or do I need to delete and recreate the volume?

Solved

0 Replies

Status changed to Awaiting Railway Response Railway 2 months ago


Status changed to Solved pierredotsol 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...