This topic created in 4829 days ago, the information mentioned may be changed or developed.
BuyVM这两天老抽，每次停机我的InnoDB数据库就完蛋了：
130215 14:34:40 InnoDB: Error: page 461 log sequence number 10364237387
InnoDB: is in the future! Current system log sequence number 10364234948.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: file read of page 531.
InnoDB: You may have to recover from a backup.
130215 14:34:40 InnoDB: Page dump in ascii and hex (16384 bytes):
我需要 导出/导入 10G的数据来恢复。。。
而如果使用MyISAM,则轻松的一个repair就搞定了。。。
InnoDB真的就是如此痛苦吗？大家如何解决这个问题的呢？
130215 14:34:40 InnoDB: Error: page 461 log sequence number 10364237387
InnoDB: is in the future! Current system log sequence number 10364234948.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: file read of page 531.
InnoDB: You may have to recover from a backup.
130215 14:34:40 InnoDB: Page dump in ascii and hex (16384 bytes):
我需要 导出/导入 10G的数据来恢复。。。
而如果使用MyISAM,则轻松的一个repair就搞定了。。。
InnoDB真的就是如此痛苦吗？大家如何解决这个问题的呢？
 |
1
y051313 Feb 15, 2013
同问，早上重启服务器后，过了5个小时才发现数据库crash了。
有什么办法至少能监测到数据库crash吗？ |
 |
2
Even Feb 15, 2013
LZ中信人？
|
Select Language