mysql crash recover

环境说明：mysql非正常关闭，致使mysql 启动时提示以下信息：

InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 3549062413

InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 4069986716

InnoDB: Page number (if stored to page already) 0,

InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0

InnoDB: Page may be a freshly allocated page

InnoDB: Database page corruption on disk or a failed

InnoDB: file read of page 426054.

InnoDB: You may have to recover from a backup.

InnoDB: It is also possible that your operating

InnoDB: system has corrupted its own file cache

InnoDB: and rebooting your computer removes the

InnoDB: error.

InnoDB: If the corrupt page is an index page

InnoDB: you can also try to fix the corruption

InnoDB: by dumping, dropping, and reimporting

InnoDB: the corrupt table. You can use CHECK

InnoDB: TABLE to scan your table for corruption.

InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html

InnoDB: about forcing recovery.

InnoDB: Ending processing because of a corrupt database page.

120902 05:20:02 mysqld_safe Number of processes running now: 0

120902 05:20:02 mysqld_safe mysqld restarted

120902  5:20:02 [Warning] /usr/local/mysql5/libexec/mysqld: ignoring option '--character-set-client-handshake' due to invalid value 'latin1'

120902  5:20:02 [Note] Plugin 'FEDERATED' is disabled.

InnoDB: Log scan progressed past the checkpoint lsn 660 1753534775

120902  5:20:02  InnoDB: Database was not shut down normally!

错误日志中一直提示这些信息

网上搜索该问题，缘由为：

数据库中表损坏致使数据访问错误，从而致使数据库崩溃；mysql中check table 发现表有损坏，但表是innodb类型不能修复

网上解决方法为：在my.ini中mysqld下添加 innodb_force_recovery=4

说明：

1(SRV_FORCE_IGNORE_CORRUPT):忽略检查到的corrupt页。 2(SRV_FORCE_NO_BACKGROUND):阻止主线程的运行，如主线程须要执行full purge操做，会致使crash。 3(SRV_FORCE_NO_TRX_UNDO):不执行事务回滚操做。 4(SRV_FORCE_NO_IBUF_MERGE):不执行插入缓冲的合并操做。 5(SRV_FORCE_NO_UNDO_LOG_SCAN):不查看重作日志，InnoDB存储引擎会将未提交的事务视为已提交。 6(SRV_FORCE_NO_LOG_REDO):不执行前滚的操做。