[MDEV-9470] Installing MariaDB over prior mysql installation fails, crashes, uses up all disk space Created: 2016-01-26  Updated: 2016-01-27  Resolved: 2016-01-27

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: 10.1.10
Fix Version/s: N/A

Type: Bug Priority: Blocker
Reporter: Lucian Hontau Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Ubuntu 14.04

Attachments: Text File mariadb-error-full.log    

 Description   

Install MariaDB on after removing mysql 5.6.27. Maria 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 upgrading mysql to 5.6.28. 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. See MySQL bug: https://bugs.mysql.com/bug.php?id=80158&thanks=2&notify=3

See attached error log.



 Comments   
Comment by Elena Stepanova [ 2016-01-26 ]

I couldn't reproduce it right away.
There isn't much in the log attached to this issue, but the log from MySQL bug report suggests you have innodb_log_file_size=75G, and there are at least two of them, so eventually it uses up disk space and ends. Since it happens both with MySQL and MariaDB new versions, it means that this configuratio is not installed by the upgrade, but is your own, maybe somebody made a typo at some point, and it will only started affecting your server after restart, which happened upon upgrade. Please check your cnf file(s).

Comment by Lucian Hontau [ 2016-01-27 ]

Thanks Elena, that was indeed the problem. It is not a bug.

Generated at Thu Feb 08 07:34:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.