This is a known issue where the volume resize did not propagate to the underlying filesystem, so Postgres still sees the old size limit despite the dashboard showing 250GB. We're working on getting the filesystem expanded for your volume, which will require a brief intervention on our side. We'll follow up here once it's done.

Hi! We've already expanded the filesystem on this volume and redeployed your Postgres service — the fix was applied via your other thread. You should now have the full 250 GB available. Let us know if you're still seeing any issues.

Team - still having this issue.

Postgres-fvhc

filesystem full after volume

resize — ENOSPC on WAL

checkpoint

▎ Volume was resized to 250GB

but ext4 filesystem is still

5GB. Need resize2fs to

expand.

▎ Service: Postgres-fvhc,

Volume ID: 49a776b6-d28c-448b

-9185-ba55363810f2

We took another look at this volume and it's showing 250 GB available on our end. Could you share what you're seeing that indicates it's still at 5 GB? A screenshot of the error or the output you're referencing would be helpful.

should be error in code, have fixed thanks.