症状: mysqldump 导出数据 或者访问某张表的或者某条数据的时候 mysql 直接 挂 了.
日志如下:
innodb: database page corruption on disk or a failed
innodb: file read of page 26400.
innodb: you may have to recover from a backup.
120217 15:45:53 innodb: page dump in ascii and hex (16384 bytes):
len 16384; hex a922822af0c7bcef6d93dadcf4f63e8331d51e7a490667defbefxxxx..................
innodb: end of page dump
f 6 pe a r zx3120217 15:45:53 innodb: page checksum 3458627726, prior-to-4.0.14-form checksum 796906866
innodb: stored checksum 2837611050, prior-to-4.0.14-form stored checksum 2410301789
innodb: page lsn 836050554 1225156574, low 4 bytes of lsn at page end 2266014174
innodb: page number (if stored to page already) 4039621871,
innodb: space id (if created with >= mysql-4.1.1 and stored already) 4222022822
innodb: database page corruption on disk or a failed
innodb: file read of page 26400.
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
innodb: about forcing recovery.
innodb: ending processing because of a corrupt database page.
解决: 具体原因不明 参考文档:
首先d:\cn.tsoft.system\mysql5.1.37\bin>mysqlcheck -uroot -pxxxx -p3306 --all-database 定位哪张表出了问题
执行结果如下:
tech_soft_drp_361new.pos_tradebill_cashredeem_item ok
mysqlcheck: got error: 2013: lost connection to mysql server during query when e
xecuting 'check table ... '
由tech_soft_drp_361new.pos_tradebill_cashredeem_item 知道下一张表是 pos_tradebill_item
将my.ini 里边的#innodb_force_recovery=1 #号去掉 重启mysql服务
然后将pos_tradebill_item 数据导出到文件(导出的时候注意导出数据的条数是否正确!)(记录select count(*) from pos_tradebill_item 与导出的条数对比)
找到pos_tradebill_item的建表语句.
删除pos_tradebill_item表
重建pos_tradebill_item表.
导入pos_tradebill_item数据(导入数据的时候将innodb_force_recovery=1重新加上#号. innodb_force_recovery=1模式不支持写)
，