| Bug #41142 | innodb errors in .log | ||
|---|---|---|---|
| Submitted: | 1 Dec 2008 4:44 | Modified: | 14 Aug 2009 7:40 |
| Reporter: | Dmitry Viazovkin | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
| Version: | 5.0.67 | OS: | Linux (fedora core 8) |
| Assigned to: | CPU Architecture: | Any | |
[1 Dec 2008 4:44]
Dmitry Viazovkin
[1 Dec 2008 10:05]
Sveta Smirnova
Thank you for the report. But version 5.0.45 is old and at least 1 related bug was fixed since. Please uprade to version 5.0.67, try with it and inform us if problem still exists. Additionally if you upgraded from version 4.0 you need to rebuild tables. See also bug #25135
[3 Dec 2008 9:23]
Dmitry Viazovkin
Upgrade to 5.0.67 done but situatinn changed from bad to panic :( 180213 lock struct(s), heap size 11595072, undo log entries 19025306 MySQL thread id 17, query id 44122 localhost acct updating delete from accounting where data <@dt InnoDB: Submit a detailed bug report to http://bugs.mysql.com InnoDB: Dump of the tablespace extent descriptor: len 40; hex 000000000000000c000540001ade000540001b0600000001ffffffffffffffffffffffffffffffff; asc InnoDB: Serious error! InnoDB is trying to free page 321215 InnoDB: though it is already marked as free in the tablespace! InnoDB: The tablespace free space info is corrupt. InnoDB: You may need to dump your InnoDB tables and recreate the whole InnoDB: database! InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. 081202 18:05:33InnoDB: Assertion failure in thread 2684947344 in file fsp0fsp.c line 2981 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. 081202 18:05:33 - mysqld got signal 11 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=67108864 read_buffer_size=2097152 max_used_connections=7 max_connections=1024 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2162688 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xa008f1c8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8195925 0x83965c1 0x8339541 0x83463e4 0x8346837 0x8317d15 0x8318db7 Stack trace seems successful - bottom reached Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 081202 18:05:33 mysqld restarted 081202 18:05:34 [Warning] The syntax for replication startup options is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead. InnoDB: Log scan progressed past the checkpoint lsn 44 3586606622 081202 18:05:34 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... InnoDB: Doing recovery: scanned up to log sequence number 44 3591849472 InnoDB: Doing recovery: scanned up to log sequence number 44 3597092352 InnoDB: Doing recovery: scanned up to log sequence number 44 3602335232 InnoDB: Doing recovery: scanned up to log sequence number 44 3607578112 InnoDB: Doing recovery: scanned up to log sequence number 44 3612820992 InnoDB: Doing recovery: scanned up to log sequence number 44 3618063872 InnoDB: Doing recovery: scanned up to log sequence number 44 3623306752 InnoDB: Doing recovery: scanned up to log sequence number 44 3628549632 InnoDB: Doing recovery: scanned up to log sequence number 44 3633792512 InnoDB: Doing recovery: scanned up to log sequence number 44 3639035392 InnoDB: Doing recovery: scanned up to log sequence number 44 3644278272 InnoDB: Doing recovery: scanned up to log sequence number 44 3649521152 InnoDB: Doing recovery: scanned up to log sequence number 44 3654764032 InnoDB: Doing recovery: scanned up to log sequence number 44 3659057252 081202 18:06:08 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 4 InnoDB: Apply batch completed 081202 18:08:28 InnoDB: Started; log sequence number 44 3659057252 081202 18:08:28 [Note] /var/lib/mysql/libexec/mysqld: ready for connections. Version: '5.0.67-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 081202 18:08:28 [Note] Slave SQL thread initialized, starting replication in log 'mail-bin.001008' at position 106562, relay log '/var/lib/mysql/binlog/slav 081202 18:08:29 [Note] Slave I/O thread: connected to master 'repl@192.168.1.232:3306', replication started in log 'mail-bin.001008' at position 106562 081202 18:08:29 [ERROR] Error reading packet from server: Client requested master to start replication from impossible position ( server_errno=1236) 081202 18:08:29 [ERROR] Got fatal error 1236: 'Client requested master to start replication from impossible position' from master when reading data from bin 081202 18:08:29 [Note] Slave I/O thread exiting, read up to log 'mail-bin.001008', position 106562 InnoDB: Dump of the tablespace extent descriptor: len 40; hex 000000000000000c000540001ade000540001b0600000001ffffffffffffffffffffffffffffffff; asc InnoDB: Serious error! InnoDB is trying to free page 321215 InnoDB: though it is already marked as free in the tablespace! InnoDB: The tablespace free space info is corrupt. InnoDB: You may need to dump your InnoDB tables and recreate the whole InnoDB: database! InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. 081202 18:08:38InnoDB: Assertion failure in thread 2684537744 in file fsp0fsp.c line 2981 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. ------------ and this error repeats again and again
[17 Dec 2008 3:19]
James Day
OPTIMIZE TABLE for this table to rebuild the index. We see this error when people haven't rebuilt the table after upgrades that change how index ordering works. That happened several times during 5.0's history. There was also a bug for prefix (partial) keys that caused this symptom, fixed for a year or two. If you still see the problem after that please let us know. James Day, MySQL Senior Support Engineer, Sun Microsystems
[29 Dec 2008 14:19]
Valeriy Kravchuk
Had you tried to execute OPTIMIZE TABLE as James suggested some time ago?
[30 Dec 2008 11:29]
Dmitry Viazovkin
Sorry but NO - there was production database and that suggestion was too late. I already made full dump, then deletion of innodb files and then full restore.
[14 Aug 2009 7:40]
Sveta Smirnova
Thank you for the feedback. Set to "Can't repeat" as not enough information to create repeatable test case was provided.
