Package: mysql-server-4.1 Version: 4.1.11a-4 Severity: grave After a power failure, InnoDB's crash recovery consistently fails to get the database is a usable state. mysqld either hangs, or segfaults. This has been tested using reiserfs, ext3, and a raw device for the tablespace. mysql 4.0 works as expected (crash recovery runs, database starts up in a usable state after power failure).
Example from syslog follows: Sep 8 14:01:08 localhost mysqld_safe[2592]: started Sep 8 14:01:08 localhost mysqld[2595]: 050908 14:01:08 InnoDB: Database was not shut down normally! Sep 8 14:01:08 localhost mysqld[2595]: InnoDB: Starting crash recovery. Sep 8 14:01:08 localhost mysqld[2595]: InnoDB: Reading tablespace information from the .ibd files... Sep 8 14:01:08 localhost mysqld[2595]: InnoDB: Restoring possible half-written data pages from the doublewrite Sep 8 14:01:08 localhost mysqld[2595]: InnoDB: buffer... Sep 8 14:01:08 localhost mysqld[2595]: 050908 14:01:08 InnoDB: Starting log scan based on checkpoint at Sep 8 14:01:08 localhost mysqld[2595]: InnoDB: log sequence number 0 683773405. Sep 8 14:01:08 localhost mysqld[2595]: InnoDB: Doing recovery: scanned up to log sequence number 0 689015808 Sep 8 14:01:08 localhost mysqld[2595]: InnoDB: Doing recovery: scanned up to log sequence number 0 689688576 Sep 8 14:01:09 localhost mysqld[2595]: InnoDB: 1 transaction(s) which must be rolled back or cleaned up Sep 8 14:01:09 localhost mysqld[2595]: InnoDB: in total 3225790 row operations to undo Sep 8 14:01:09 localhost mysqld[2595]: InnoDB: Trx id counter is 0 1792 Sep 8 14:01:09 localhost mysqld[2595]: 050908 14:01:09 InnoDB: Starting an apply batch of log records to the database... Sep 8 14:01:09 localhost mysqld[2595]: InnoDB: Progress in percents: 0 1 2 3 050908 14:01:09 InnoDB: Error: page 42497 log sequence number 0 690226205 Sep 8 14:01:09 localhost mysqld[2595]: InnoDB: is in the future! Current system log sequence number 0 689688483. Sep 8 14:01:09 localhost mysqld[2595]: InnoDB: Your database may be corrupt. Sep 8 14:01:09 localhost mysqld[2595]: 050908 14:01:09 InnoDB: Error: page 42498 log sequence number 0 690709217 Sep 8 14:01:09 localhost mysqld[2595]: InnoDB: is in the future! Current system log sequence number 0 689688483. Sep 8 14:01:09 localhost mysqld[2595]: InnoDB: Your database may be corrupt. Sep 8 14:01:09 localhost mysqld[2595]: 050908 14:01:09 InnoDB: Error: page 42499 log sequence number 0 690683405 Sep 8 14:01:09 localhost mysqld[2595]: InnoDB: is in the future! Current system log sequence number 0 689688483. Sep 8 14:01:09 localhost mysqld[2595]: InnoDB: Your database may be corrupt. [ ... ] Sep 8 14:01:23 localhost mysqld[2595]: 98 99 Sep 8 14:01:23 localhost mysqld[2595]: InnoDB: Apply batch completed Sep 8 14:01:23 localhost mysqld[2595]: InnoDB: Starting rollback of uncommitted transactions Sep 8 14:01:23 localhost mysqld[2595]: InnoDB: Rolling back trx with id 0 1393, 3225790 rows to undo Sep 8 14:01:23 localhost mysqld[2595]: InnoDB: Progress in percents: 1050908 14:01:23 InnoDB: Error: page 15398 log sequence number 0 690059220 Sep 8 14:01:23 localhost mysqld[2595]: InnoDB: is in the future! Current system log sequence number 0 689735039. Sep 8 14:01:23 localhost mysqld[2595]: InnoDB: Your database may be corrupt. Sep 8 14:01:34 localhost mysqld[2595]: 2mysqld got signal 11; Sep 8 14:01:34 localhost mysqld[2595]: This could be because you hit a bug. It is also possible that this binary Sep 8 14:01:34 localhost mysqld[2595]: or one of the libraries it was linked against is corrupt, improperly built, Sep 8 14:01:34 localhost mysqld[2595]: or misconfigured. This error can also be caused by malfunctioning hardware. Sep 8 14:01:34 localhost mysqld[2595]: We will try our best to scrape up some info that will hopefully help diagnose Sep 8 14:01:34 localhost mysqld[2595]: the problem, but since we have already crashed, something is definitely wrong Sep 8 14:01:34 localhost mysqld[2595]: and this may fail. Sep 8 14:01:34 localhost mysqld[2595]: Sep 8 14:01:34 localhost mysqld[2595]: key_buffer_size=0 Sep 8 14:01:34 localhost mysqld[2595]: read_buffer_size=131072 Sep 8 14:01:34 localhost mysqld[2595]: max_used_connections=0 Sep 8 14:01:34 localhost mysqld[2595]: max_connections=100 Sep 8 14:01:34 localhost mysqld[2595]: threads_connected=0 Sep 8 14:01:34 localhost mysqld[2595]: It is possible that mysqld could use up to Sep 8 14:01:34 localhost mysqld[2595]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K Sep 8 14:01:34 localhost mysqld[2595]: bytes of memory Sep 8 14:01:34 localhost mysqld[2595]: Hope that's ok; if not, decrease some variables in the equation. Sep 8 14:01:34 localhost mysqld[2595]: Sep 8 14:01:34 localhost mysqld[2595]: thd=(nil) Sep 8 14:01:34 localhost mysqld[2595]: Attempting backtrace. You can use the following information to find out Sep 8 14:01:34 localhost mysqld[2595]: where mysqld died. If you see no messages after this, something went Sep 8 14:01:34 localhost mysqld[2595]: terribly wrong... Sep 8 14:01:34 localhost mysqld[2595]: Cannot determine thread, fp=0xbfffd8ec, backtrace may not be correct. Sep 8 14:01:34 localhost mysqld[2595]: Stack range sanity check OK, backtrace follows: Sep 8 14:01:34 localhost mysqld[2595]: 0x81893bf Sep 8 14:01:34 localhost mysqld[2595]: 0xffffe420 Sep 8 14:01:34 localhost mysqld[2595]: 0xbfffdda0 Sep 8 14:01:34 localhost mysqld[2595]: 0x83505d9 Sep 8 14:01:34 localhost mysqld[2595]: 0x8363b88 Sep 8 14:01:34 localhost mysqld[2595]: 0x8363fd5 Sep 8 14:01:34 localhost mysqld[2595]: 0x834166a Sep 8 14:01:34 localhost mysqld[2595]: 0x8340ba4 Sep 8 14:01:34 localhost mysqld[2595]: 0x833b11c Sep 8 14:01:34 localhost mysqld[2595]: 0x833a9b7 Sep 8 14:01:34 localhost mysqld[2595]: 0x8312001 Sep 8 14:01:34 localhost mysqld[2595]: 0x831125c Sep 8 14:01:34 localhost mysqld[2595]: 0x837dc39 Sep 8 14:01:34 localhost mysqld[2595]: 0x83ac6e0 Sep 8 14:01:34 localhost mysqld[2595]: 0x82f3156 Sep 8 14:01:34 localhost mysqld[2595]: 0x821bb0e Sep 8 14:01:34 localhost mysqld[2595]: 0x820cee5 Sep 8 14:01:34 localhost mysqld[2595]: 0x818cc15 Sep 8 14:01:34 localhost mysqld[2595]: 0x8189ab5 Sep 8 14:01:34 localhost mysqld[2595]: 0x48115970 Sep 8 14:01:34 localhost mysqld[2595]: 0x810cef1 -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages mysql-server-4.1 depends on: ii adduser 3.63 Add and remove users and groups ii debconf 1.4.30.13 Debian configuration management sy ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libdbi-perl 1.46-6 Perl5 database interface by Tim Bu ii libgcc1 1:3.4.3-13 GCC support library pn libmysqlclient14 Not found. ii libncurses5 5.4-4 Shared libraries for terminal hand ii libreadline4 4.3-11 GNU readline and history libraries ii libstdc++5 1:3.3.5-13 The GNU Standard C++ Library v3 ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra ii mailx 1:8.1.2-0.20040524cvs-4 A simple mail user agent pn mysql-client-4.1 Not found. ii mysql-common 4.0.24-10 mysql database common files (e.g. ii passwd 1:4.0.3-31sarge5 change and administer password and ii perl 5.8.4-8 Larry Wall's Practical Extraction ii psmisc 21.5-1 Utilities that use the proc filesy ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
