mysql 2103_Mysql 备份 lost connection 服务器自动关闭 2103

昨天在向表中添加字段时，电脑自动关闭了(定的时间)，今天再访问这张表，没几秒钟，mysql就关闭了，重启还是这样,

错误日志:

InnoDB: Database page corruption on disk or a failed

InnoDB: file read of page 65784.

InnoDB: You may have to recover from a backup.

100923 23:50:32  InnoDB: Page dump in ascii and hex (16384 bytes):

len 16384; hex      _ c        ;

InnoDB: End of page dump

100923 23:50:32  InnoDB: Page checksum 1440584919, prior-to-4.0.14-form checksum 2879555096

InnoDB: stored checksum 584289623, prior-to-4.0.14-form stored checksum 2879555096

InnoDB: Page lsn 12 2261320684, low 4 bytes of lsn at page end 2261320684

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

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

InnoDB: Page may be an index page where index id is 0 2162

InnoDB: (index "PRIMARY" of table "ssq"."whole")

InnoDB: Database page corruption on disk or a failed

InnoDB: file read of page 65784.

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.

我发现别的表没有问题,这张问题表执行单独执行也没有问题,当使用selelct count(*) from tablename;就出问题,

当我试图备份这张表的时候,提示: lost connection to mysql server during query when dumping table at row 441747;单独查询这一行也没有问题,我该怎么办?

2010年9月24日 14:46