a month ago
Production MySQL database crashed mid-upgrade (9.4.0 → 9.7.2) due to disk space exhaustion (posix_fallocate... Operating system error number 28, ENOSPC). The database won't restart - it fails immediately with the same disk-full errors during crash recovery / upgrade completion. Dashboard shows only 729MB/8GB used, but MySQL is reporting the disk as completely full. Need the volume resized or the disk-full condition resolved so the database can complete its startup. Please help!
1 Replies
a month ago
The volume attached to your MySQL service is provisioned at 500 MB, which is what MySQL is exhausting during the upgrade's crash recovery (InnoDB redo log replay and undo tablespace creation need temporary headroom beyond the ~163 MB of stored data). You can resize it from the volume settings in your project dashboard, up to 5 GB on the Hobby plan, and the resize applies while the service is stopped, so MySQL will have the space it needs on the next restart.
Status changed to Awaiting User Response Railway • about 1 month ago
25 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 25 days ago