innodb.innodb_bug52745 sporadically fails in 5.5.11

Bug #746526 reported by Alexey Kopytov on 2011-03-31
This bug report is a duplicate of:  Bug #756391: The innodb.innodb-zip fails in 5.5.11. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
percona-projects-qa
Undecided
Unassigned

Bug Description

I get the following server crash when running innodb.innodb_bug52745 on Mac OS X. It may be applicable to other non-Linux platforms as well.

innodb.innodb_bug52745 [ fail ]
        Test ended at 2011-03-31 19:44:45

CURRENT_TEST: innodb.innodb_bug52745
mysqltest: At line 67: query 'INSERT INTO bug52745 SET
col40='0000-00-00 00:00:00',
col51=16547,
col53='7711484',
col54=-28604,
col55='7112612',
col56='wakefulness\'',
col57=repeat('absorbefacient\'',106),
col58=11027,
col59='AM09gW7',
col60=repeat('Noelani\'',16),
col61='2520576',
col62='substitutiv',
col63='19950106155112',
col64=-12038,
col65='86238806',
col66='19600719080256',
col68=repeat('Sagittarius\'',54),
col69='38943902',
col70=1232,
col71='Elora\'',
col74=repeat('zipp',11),
col75='0',
col76=23254,
col78=13247,
col79='56219',
col80='20500609035724',
col81=11632,
col82=7,
col84=-23863,
col85=6341,
col87='HZdkf.4 s7t,5Rmq 8so fmr,ruGLUG25TrtI.yQ 2SuHq0ML7rw7.4 b2yf2E5TJxOtBBZImezDnzpj,uPYfznnEUDN1e9aQoO 2DsplB7TFWy oQJ br HLF :F,eQ p4i1oWsr lL3PG,hjCz6hYqN h1QTjLCjrv:QCdSzpYBibJAtZCxLOk3l6Blsh.W',
col88=16894,
col89=6161,
col90=repeat('gale',48)' failed: 2013: Lost connection to MySQL server during query

The result from queries just before the failure was:
< snip >
col75 bit(34) DEFAULT NULL,
col76 float unsigned zerofill DEFAULT NULL,
col77 year(2) DEFAULT NULL,
col78 tinyint(3) unsigned DEFAULT NULL,
col79 set('msfheowh','tbpxbgf','by','wahnrjw','myqfasxz','rsokyumrt') CHARACTER SET latin2 DEFAULT NULL,
col80 datetime DEFAULT NULL,
col81 smallint(6) DEFAULT NULL,
col82 enum('xtaurnqfqz','rifrse','kuzwpbvb','niisabk','zxavro','rbvasv','','uulrfaove','','') DEFAULT NULL,
col83 bigint(20) unsigned zerofill DEFAULT NULL,
col84 float unsigned zerofill DEFAULT NULL,
col85 double DEFAULT NULL,
col86 enum('ylannv','','vlkhycqc','snke','cxifustp','xiaxaswzp','oxl') CHARACTER SET latin1 COLLATE latin1_german2_ci DEFAULT NULL,
col87 varbinary(221) DEFAULT NULL,
col88 double unsigned DEFAULT NULL,
col89 float unsigned zerofill DEFAULT NULL,
col90 tinyblob
) ENGINE=InnoDB DEFAULT CHARSET=latin1 ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=1;
Warnings:
Note 1291 Column 'col82' has duplicated value '' in ENUM
Note 1291 Column 'col82' has duplicated value '' in ENUM

More results from queries before failure can be found in /Users/kaa/src/percona/5.5/Percona-Server-debug/mysql-test/var/log/innodb_bug52745.log

Server [mysqld.1 - pid: 9904, winpid: 9904, exit: 256] failed during test run
Server log from this test:
----------SERVER LOG START-----------
110331 18:44:40 [Warning] Setting lower_case_table_names=2 because file system for /Users/kaa/src/percona/5.5/Percona-Server-debug/mysql-test/var/mysqld.1/data/ is case insensitive
110331 18:44:40 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
110331 18:44:40 InnoDB: The InnoDB memory heap is disabled
110331 18:44:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110331 18:44:40 InnoDB: Compressed tables use zlib 1.2.3
110331 18:44:40 InnoDB: Initializing buffer pool, size = 32.0M
110331 18:44:40 InnoDB: Completed initialization of buffer pool
110331 18:44:40 InnoDB: highest supported file format is Barracuda.
110331 18:44:40 InnoDB: Waiting for the background threads to start
110331 18:44:41 Percona XtraDB (http://www.percona.com) 1.1.5-12.1 started; log sequence number 1597945
110331 18:44:41 [Note] Event Scheduler: Loaded 0 events
110331 18:44:41 [Note] /Users/kaa/src/percona/5.5/Percona-Server-debug/sql/mysqld: ready for connections.
Version: '5.5.10-debug-log' socket: '/Users/kaa/src/percona/5.5/Percona-Server-debug/mysql-test/var/tmp/mysqld.1.sock' port: 13000 Source distribution
InnoDB: DEBUG: update_statistics for test/bug52745.
InnoDB: DEBUG: update_statistics for test/bug52745.
110331 18:44:42 InnoDB: Assertion failure in thread 4401729536 in file /Users/kaa/src/percona/5.5/Percona-Server/storage/innobase/buf/buf0buf.c line 2422
InnoDB: Failing assertion: buf_page_in_file(bpage)
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110331 18:44:42 - mysqld got signal 6 ;
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=1048576
read_buffer_size=131072
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60917 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
stack_bottom = 0x0 thread_stack 0x40000
0 mysqld 0x00000001003874c9 my_print_stacktrace + 57
1 mysqld 0x0000000100144ed2 handle_segfault + 834
2 libSystem.B.dylib 0x00007fff8393d66a _sigtramp + 26
3 mysqld 0x0000000100000000 __dso_handle + 0
4 mysqld 0x000000010014e0cf _Z11mysqld_mainiPPc + 2383
5 mysqld 0x00000001000221a0 start + 52
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.
Writing a core file
----------SERVER LOG END-------------

Alexey Kopytov (akopytov) wrote :
Download full text (29.9 KiB)

The failure is sporadic and can be observed on Linux as well:

innodb.innodb_bug52745 [ fail ]
        Test ended at 2011-04-10 04:33:53

CURRENT_TEST: innodb.innodb_bug52745
mysqltest: At line 67: query 'INSERT INTO bug52745 SET
col40='0000-00-00 00:00:00',
col51=16547,
col53='7711484',
col54=-28604,
col55='7112612',
col56='wakefulness\'',
col57=repeat('absorbefacient\'',106),
col58=11027,
col59='AM09gW7',
col60=repeat('Noelani\'',16),
col61='2520576',
col62='substitutiv',
col63='19950106155112',
col64=-12038,
col65='86238806',
col66='19600719080256',
col68=repeat('Sagittarius\'',54),
col69='38943902',
col70=1232,
col71='Elora\'',
col74=repeat('zipp',11),
col75='0',
col76=23254,
col78=13247,
col79='56219',
col80='20500609035724',
col81=11632,
col82=7,
col84=-23863,
col85=6341,
col87='HZdkf.4 s7t,5Rmq 8so fmr,ruGLUG25TrtI.yQ 2SuHq0ML7rw7.4 b2yf2E5TJxOtBBZImezDnzpj,uPYfznnEUDN1e9aQoO 2DsplB7TFWy oQJ br HLF :F,eQ p4i1oWsr lL3PG,hjCz6hYqN h1QTjLCjrv:QCdSzpYBibJAtZCxLOk3l6Blsh.W',
col88=16894,
col89=6161,
col90=repeat('gale',48)' failed: 2013: Lost connection to MySQL server during query

The result from queries just before the failure was:
< snip >
col75 bit(34) DEFAULT NULL,
col76 float unsigned zerofill DEFAULT NULL,
col77 year(2) DEFAULT NULL,
col78 tinyint(3) unsigned DEFAULT NULL,
col79 set('msfheowh','tbpxbgf','by','wahnrjw','myqfasxz','rsokyumrt') CHARACTER SET latin2 DEFAULT NULL,
col80 datetime DEFAULT NULL,
col81 smallint(6) DEFAULT NULL,
col82 enum('xtaurnqfqz','rifrse','kuzwpbvb','niisabk','zxavro','rbvasv','','uulrfaove','','') DEFAULT NULL,
col83 bigint(20) unsigned zerofill DEFAULT NULL,
col84 float unsigned zerofill DEFAULT NULL,
col85 double DEFAULT NULL,
col86 enum('ylannv','','vlkhycqc','snke','cxifustp','xiaxaswzp','oxl') CHARACTER SET latin1 COLLATE latin1_german2_ci DEFAULT NULL,
col87 varbinary(221) DEFAULT NULL,
col88 double unsigned DEFAULT NULL,
col89 float unsigned zerofill DEFAULT NULL,
col90 tinyblob
) ENGINE=InnoDB DEFAULT CHARSET=latin1 ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=1;
Warnings:
Note 1291 Column 'col82' has duplicated value '' in ENUM
Note 1291 Column 'col82' has duplicated value '' in ENUM

More results from queries before failure can be found in /home/alexey.kopytov/src/percona/5.5.11/Percona-Server-debug/mysql-test/var/log/innodb_bug52745.log

Server [mysqld.1 - pid: 9133, winpid: 9133, exit: 256] failed during test run
Server log from this test:
----------SERVER LOG START-----------
InnoDB: DEBUG: update_statistics for test/bug52745.
InnoDB: DEBUG: update_statistics for test/bug52745.
110410 14:33:53 InnoDB: Assertion failure in thread 1094277440 in file /home/alexey.kopytov/src/percona/5.5.11/Percona-Server/storage/innobase/buf/buf0buf.c line 2422
InnoDB: Failing assertion: buf_page_in_file(bpage)
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.5/en/forcing-innodb-recovery.html
InnoDB:...

summary: - innodb.innodb_bug52745 crashes the server on Mac OS X
+ innodb.innodb_bug52745 sporadically fails in 5.5.11
Changed in percona-projects-qa:
assignee: nobody → Yasufumi Kinoshita (yasufumi-kinoshita)

Alexey,

Your Linux case seems duplicate of bug756391.
I think it was fixed already.

Alexey Kopytov (akopytov) wrote :

Yes, not repeatable with the fix for bug #756391.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers