Hey there! We've found the following might help you get unblocked faster:

• 🧵 Help increasing volume size

• 🧵 Postgress DB volume issue

• 🧵 Increasing Volume Size

If you find the answer from one of these, please let us know by solving the thread!

I'm having this exact same problem. My data size is around 60MB but the volume size was at 243MB. Then last night at 3:30 AM it started growing steadily until it hit the 500MB limit at around 1:12 PM even though my application and database were idle during this time. Increasing the volume size isn't the answer if it's just going to keep growing unctrolled.

Hello,

The actual size of the /var/lib/mysql volume mount is 399MB, plus some extra reported size for the filesystem overheard.

So the reported usage is correct and accurate.

Since we are not misreporting anything on our end, I will open this thread up to the community, where users may have ideas on how to clear out some MySQL usage.

Best,
Brody

just realized his db is mysql, mine is postgresql, but similar issue. I opened a separate thread for mine. my db volume is at 500MB, so you'll find basically the same thing in my case, but I don't understand WHY it's taking up so much space when my db backup is only 60MB.

what are the file size or use of your MySQL Bin Files ? the SQL looks at the total usage, not just the size of your database tables.

https://www.cyberciti.biz/faq/what-is-mysql-binary-log/

nevermind, I figured out what happened in my case - problem in my application - wasn't idle after all.

hi brody,

If my whole MySQL dump, including the sys schema is 60.4MB, how can the volume be at 95% of the total 500MB? I have double checked this. Exported everything using Workbench.

Please enlighten me as to how I could be checking what is taking the remaining space, up to your reported 399MB? (which excludes any filesystem overheard)

binlog is OFF in my MySQL instance. I ran "SHOW VARIABLES LIKE 'log_bin'" and "SHOW BINARY LOGS" to confirm this.

innodb_file_per_table is ON.

Then I also ran this query and confirm that whole DB size is not over 100 MB in practice:

SELECT table_schema AS "Database",

ROUND(SUM(data_length + index_length) / 1024 / 1024, 2) AS "Size_MB"

FROM information_schema.tables

GROUP BY table_schema

ORDER BY Size_MB DESC;

What else could it be?

Still looking for a meaningful answer here.

Could you please check the specifics of what exactly adds up to those 399MB? It would be easy for someone at Railway to verify.

Thank you