| Bug #56359 | Assertion failure in LRU handler | ||
|---|---|---|---|
| Submitted: | 30 Aug 2010 10:29 | Modified: | 22 Aug 2015 11:31 |
| Reporter: | Jonathon Coombes | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
| Version: | 5.0.72sp1 | OS: | Linux |
| Assigned to: | Marko Mäkelä | CPU Architecture: | Any |
| Tags: | assertion, innodb, LRU | ||
[7 Sep 2010 6:04]
Marko Mäkelä
It looks like there could be two errors in the error log. One would be the buf_pool->LRU list corruption, and another would be an (incomplete) page dump from some other thread. Can you please attach the full error log since the server was started? There have been many changes to the buf_pool->LRU list management in InnoDB Plugin 1.0 (available in MySQL 5.1). At least one had something to do with the LRU_old boundary. It is possible that this bug has been fixed in newer 5.0 releases. I can try to check that, once I have the full error log.
[8 Sep 2010 7:57]
Marko Mäkelä
I cannot see any relevant changes to the LRU bug in the 5.0 or 5.1 code bases. The only relevant changes I see are in InnoDB Plugin 1.0 (which is distributed with recent 5.1 releases):
Debug code:
------------------------------------------------------------
revno: 0.3.1190
revision-id: svn-v4:16c675df-0fcb-4bc9-8058-dcc011a37293:branches/zip:2596
parent: svn-v4:16c675df-0fcb-4bc9-8058-dcc011a37293:branches/zip:2595
committer: marko
timestamp: Mon 2008-08-18 18:06:33 +0000
message:
branches/zip: buf_page_set_old(): Add the assertion ut_ad(bpage->in_LRU_list).
Adjust the callers where necessary:
buf_LRU_add_block_to_end_low() and buf_LRU_add_block_low().
------------------------------------------------------------
revno: 0.3.1191
revision-id: svn-v4:16c675df-0fcb-4bc9-8058-dcc011a37293:branches/zip:2597
parent: svn-v4:16c675df-0fcb-4bc9-8058-dcc011a37293:branches/zip:2596
committer: marko
timestamp: Mon 2008-08-18 18:28:20 +0000
message:
branches/zip: Introduce UNIV_LRU_DEBUG for debugging the LRU buffer pool
cache, especially buf_pool->LRU_old and bpage->old.
(plus many other changes to the LRU code)
Bug fix:
------------------------------------------------------------
revno: 0.3.1908
revision-id: svn-v4:16c675df-0fcb-4bc9-8058-dcc011a37293:branches/zip:6111
parent: svn-v4:16c675df-0fcb-4bc9-8058-dcc011a37293:branches/zip:6110
committer: marko
timestamp: Thu 2009-10-29 11:04:11 +0000
message:
branches/zip: Fix corruption of buf_pool->LRU_old and improve debug assertions.
This was reported as Issue #381.
It would be hard to port all these changes to the built-in InnoDB in 5.1, let alone to 5.0. The LRU_old assertion failure is likely fixed in the InnoDB Plugin of MySQL 5.1 and in MySQL 5.5+.
[7 Oct 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Description: InnoDB: Assertion failure in thread 1205930304 in file buf0lru.c line 219 InnoDB: Failing assertion: block->in_LRU_list 000000000000000000 00000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 InnoDB: We intentionally gen erate 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. 100827 10:13:47 - 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=8384512 read_buffer_size=131072 max_used_connections=616 max_connections=920 threads_connected=210 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2010100 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 0000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000 00 00 00000000000000000000000000 00 00000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000 00thd=0x2aad783983b0 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=0x2aad783983b0, backtrace may not be correct. Bogus stack limit or frame pointer, fp=0x2aad783983b0, stack_bottom=0x47e10000, thread_stack=262144, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x2928bbc0 = SELECT PageConfiguration.ConfigurationID, PageConfiguration.TemplateSetID, PageConfiguration.StoreID, PageConfiguration.PersistenceID, PageConfiguration.Name, PageConfiguration.D efaultInd, PageConfiguration.Configuration FROM PageConfiguration WHERE PageConfiguration.TemplateSetID = 18288 AND PageConfiguration.StoreID = 14870 AND PageConfiguration.PersistenceID = 'cataloglist' AND Pag eConfiguration.DefaultInd = 1 thd->thread_id=3363004 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. Note that the assertion failure appears part way through a corrupted page dump after getting an initial message: InnoDB: Page directory corruption: supremum not pointed to How to repeat: Not sure