120129 14:45:28  InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 994296725:2257927023, should be 0:8511!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 8511.
InnoDB: You may have to recover from a backup.
120129 14:45:28  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 81953b3186953b6fae953bd1ae953b22b7953bc5b9953b93bc953b85bd953b43c3953b43c3953b89c7;InnoDB: End of page dump
120129 14:45:28  InnoDB: Page checksum 2404129754, prior-to-4.0.14-form checksum 2892012813
InnoDB: stored checksum 2174040881, prior-to-4.0.14-form stored checksum 3001170866
InnoDB: Page lsn 3080010693 3113565075, low 4 bytes of lsn at page end 3034725133
InnoDB: Page number (if stored to page already) 2257927023,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 994296725
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 8511.
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.

参考：http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html