On Dec 4, 2003, at 23:55, Brion Vibber wrote:
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 1289395.
InnoDB: You may have to recover from a backup.
I'm still fighting with this. Docs recommend rebooting the machine to
try to see if the operating system's buffer caches are corrupted and
the file itself is fine; I haven't tried that (I don't even know for
sure if the machine will come back if I try it, and we have no way to
power cycle this machine remotely yet). I did try reading a huge
portion of the innodb data file through memory to see if it would clear
out the particular page, and this had no affect.
I tried the 'max' and 'standard' AMD64 binary builds of MySQL 4.0.16,
and then compiled it from source. Switching these has no affect.
The DB will croak spontaneously from time to time, and I can
consistently provoke it by running "check table cur" on enwiki.
I tried to see if I could pull together a fresh copy of everything by
rebuilding the databases from the binlog, but this doesn't seem to
include the statements to create databases...? or something? and I'm
not sure what exactly is required to make such a rebuild happen
cleanly.
However, every query that updated any data in the last three days _is_
in the binlog, so in the worst case it should be possible to rebuild
it...
I'm going to try to bang on this for a whille longer...
-- brion vibber (brion @
pobox.com)