… of log recovery. As it is very nasty option I wanted to check if this is really required by trying lower recovery settings… innodb_force_recovery=0 allowed it to start normally and I could rebuild affected tables my “normal way”. So when dealing with Innodb recovery for bad corruptions you may want to: – Start with lower innodb_force_recovery settings and see which one…

… avoid dumping the data and find some other way to recovery. Examining Innodb page content and crash information we figured out it… buffer. I think it would be nice for Innodb to have some additional recovery options for example for skipping over insert buffer or… with innodb_force_recovery=4 was confirmed to be added in 5.0.33, meaning you could not really recover corrupted Innodb tables…

… old table and convert new table back to Innodb after restarting without innodb_force_recovery option. You can also rename the old table in… higher innodb_force_recovery modes to block purging activity, insert buffer merge or recovery from transactional logs all together. Though the lower recovery mode… work well – in this case you may wish to use Innodb Recovery Toolkit which is also helpful in cases you’ve want…

… MySQL 4.1 and above the longest part of recovery after crash for Innodb tables could be UNDO stage – it was happening… with restarts more than crash recovery as it presents in normal restarts as well – “Opening Tables”. As Innodb has to recompute the… of MySQL 5.0 It would be great if Innodb would finally optionally store stats, same as MyISAM so one could recompute…

… out detailed guide on tuning innodb buffer pool innodb_log_file_size – This depends on your recovery speed needs but 256M seems to be a good balance between reasonable recovery time and good performance innodb_log_buffer… tables use this option, so you will not have uncontrolled innodb main tablespace growth which you can’t reclaim. This option was added…