Bug #5626 mysql crashes when backing up InnoDB table with mysqldump with locking
Submitted: 17 Sep 2004 10:40 Modified: 17 Sep 2004 12:05
Reporter: vaclav bilek Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:4.0.21 OS:Linux (linux debian 3.0)
Assigned to: CPU Architecture:Any

[17 Sep 2004 10:40] vaclav bilek
Description:
# mysqldump -u root -p -l test2 User > /tmp/test2
mysqldump: Can't get CREATE TABLE for table `User` (Lost connection to MySQL server during query)

erorlog:
key_buffer_size=268435456
read_buffer_size=1044480
max_used_connections=0
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 466543 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x87067c8
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=0xbe7fef18, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80db90f
0x40034f54
0x81407ac
0x80fbdcf
0x814f3d3
0x80e8cc2
0x80eb438
0x80e6e61
0x80ecb1d
0x80e6117
0x400320ba
0x401c8d6a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8709a88 = show create table `User`
thd->thread_id=3

How to repeat:
create database test2;
use test2
CREATE TABLE `User` (
  `firstname` varchar(20) NOT NULL default '',
  `surname` varchar(20) NOT NULL default '',
  `user` varchar(16) NOT NULL default '',
  `passwd` varchar(32) NOT NULL default '',
  `email` varchar(64) NOT NULL default '',
  `access_level` enum('banned','user','root') NOT NULL default 'user',
  `created` datetime NOT NULL default '0000-00-00 00:00:00',
  `id` int(10) unsigned NOT NULL auto_increment,
  PRIMARY KEY  (`id`),
  UNIQUE KEY `user` (`user`)
) TYPE=InnoDB;

mysqldump -l test2 User
[17 Sep 2004 10:41] vaclav bilek
..
[17 Sep 2004 12:05] Heikki Tuuri
Hi!

This is a duplicate of Bug #5538 that is already fixed in the current 4.0 source tree.

Workaround: use --quick and --single-transaction options.

Thank you,

Heikki