Bug #80158 MySQL eats up all available disk space upon upgrade, fails to start

• Submitted: 26 Jan 2016 17:16
• Modified: 27 Jan 2016 15:55
• Reporter: Lucian Hontau
• Status: Not a Bug
• Category: MySQL Server
• Severity: S1 (Critical)
• Version: 5.6.28
• OS: Ubuntu (14.04)
• CPU Architecture: Any
• Tags: crash, disk space, out of space, upgrade

[26 Jan 2016 17:16] Lucian Hontau

Description:
Upgrade from 5.6.27 to 5.6.28 ubuntu packages (happens unattended on systems with security updates enabled). MySQL will eat up disk space until it runs out and then crash. Binlogs are turned OFF but the binlog files grow until they eat all space. Once the first one is done growing, another file grows. This also happens if completely removing mysql and installing mariadb 10.1. Once it fails, it'll restart and eat up all the disk space (and CPU in the meantime) again. Over and over and over and over again. Happens with mysql 5.6, mariadb 10.1. 

How to repeat:
Upgrade a mysql install or install mysql a new on top of a previous install. It's guaranteed to happen. 

Suggested fix:
Don't have it eat up all the disk space for absolutely no reason whatsoever.

[26 Jan 2016 17:17] Lucian Hontau

Error logs.

Attachment: mysql-error.log (application/octet-stream, text), 12.00 KiB.

[26 Jan 2016 17:18] Lucian Hontau

See attached log.

[26 Jan 2016 17:35] Lucian Hontau

See MariaDB bug: https://mariadb.atlassian.net/browse/MDEV-9470

[26 Jan 2016 17:55] Lucian Hontau

Same thing happens with the official MySQL 5.6.28 version downloaded from the official repositories.

[27 Jan 2016 1:07] MySQL Verification Team

doesn't look like a bug to me.  Please upload my.cnf.

"Cannot set log file ./ib_logfile1 to size 76800 MB"

That seems excessively high.

[27 Jan 2016 15:55] Lucian Hontau

Thanks Shane. innodb_log_file_size=75G was indeed the problem. It's not a bug.