InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 1289395. InnoDB: You may have to recover from a backup. 031205 7:15:02 InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex d40044c50013acb30013acb10013acb400000006f5bb4a7745bf00000000000000000000 00000002380500070 [snip some dumped data showing various snippets of wiki pages] 93.170.250.70]] 11:06,.t.e.0....Jw;InnoDB: End of page dump 031205 7:15:02 InnoDB: Page checksum 1585856272, prior-to-4.0.14-form checksum 2519793357 InnoDB: stored checksum 3556787397, prior-to-4.0.14-form stored checksum 2519793357 InnoDB: Page lsn 6 4122692215, low 4 bytes of lsn at page end 4122692215 InnoDB: Page may be an update undo log page InnoDB: Page may be an index page where index id is 0 47 InnoDB: and table enwiki/cur index cur_id InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 1289395. 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: Look also at section 6.1 of InnoDB: http://www.innodb.com/ibman.html about InnoDB: forcing recovery. InnoDB: Ending processing because of a corrupt database page.
It tried to restart itself several times with the same error, then gave up. A manual restart of mysql got it back on its feet, at least mostly...?
-- brion vibber (brion @ pobox.com)