Hi,
I just upgraded my installation of MySQL 4.1.8 (on Windows XP) to
4.1.10, and the server fails to start up now. The following is a
relevant bit from the error logfile (I've removed the InnoDB page
dumps for readability - they're all 0's, FWIW):
050216 14:42:21 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
050216 14:42:21 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 983155.
InnoDB: Doing recovery: scanned up to log sequence number 0 983155
InnoDB: Page directory corruption: supremum not pointed to
050216 14:42:21 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex ... asc ... ;InnoDB: End of page dump
050216 14:42:21 InnoDB: Page checksum 1575996416,
prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page directory corruption: supremum not pointed to
050216 14:42:21 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex ... asc ... ;InnoDB: End of page dump
050216 14:42:21 InnoDB: Page checksum 1575996416,
prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
050216 14:42:21 [ERROR] mysqld-nt: Got signal 11. Aborting!
050216 14:42:21 [ERROR] Aborting
050216 14:42:21 [Note] mysqld-nt: Shutdown complete
Any ideas why this might happen, or whether this (the segfault, in
particular) may be a bug in MySQL?
Thanks!
--
schnee
