We just ran into a nasty InnoDB bug that only seems to exist in MySQL 5.5.25:
An InnoDB update that modifies a rows primary key can trigger some recursive behavior that creates new rows until all disk space is exceeded. This does not affect all primary key updates in general but only gets triggered when a few other conditions are also met, so you're not too likely to run into it, but if you do your mysqld server will waste a lot of IO bandwidth and storage space on this and will usually eventually run out of disk space.
Submitted by hartmut on June 27, 2012 - 8:45am GMT
SkySQL and the SkySQL logo are trademarks of SkySQL Corporation Ab. Oracle, MySQL, and InnoDB are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.