# Avoiding InnoDB corruption **URL:** \ **Category:** Other MySQL® Questions\ **Created:** [January 20, 2013, 2:03pm UTC](https://forums.percona.com/t/avoiding-innodb-corruption/1969 "2013-01-20T14:03:02Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![scex](https://avatars.discourse-cdn.com/v4/letter/s/278dde/32.png) [@scex](https://forums.percona.com/u/scex)\ **Post date:** [January 20, 2013, 2:03pm UTC](https://forums.percona.com/t/avoiding-innodb-corruption/1969/1 "2013-01-20T14:03:02Z")
Hi all, we just got hit twice by mysql bug 61104 (InnoDB: Failing assertion: page\_get\_n\_recs(page) \> 1) which not only crashes the mysql server (very bad) but leaves the innodb files in such a state that the cannot be recovered (very very bad), at least not without special tools. Fortunately our backup/failover strategoy worked as designed. So far so good, we’re now migrating to latest and greatest 5.5.29 which may or may not solve the issue and set innodb\_change\_buffering=inserts which may or may not solve the issue. At least we’ve done our best with regards to the aforementioned bug. In a broader sense this means we’ve learned that there are settings in the my.cnf file like innodb\_change\_buffering that may decrease performance but avoid some crashes. Is anybody aware of other DEFAULT settings that are known to create problems (I’m not talking about settings like innodb-flush-log-at-trx-commit or sync\_binlog which have safe defaults). Thanks for the advice and best regards Holger