Hi there, I'm using mysql on a Mandrake 9.2 server. As I wanted to move to InnoDB tables and the standard mysql-4.0.15 on Mandrake doesn't have that compiled in, I obtained the most recent (4.0.21) version from mysql.com, uninstalled the Mandrake version and installed the mysql.com one. I assumed I could still use my stuff in /var/lib/mysql.
I can actually create InnoDB tables, add and select data and all that, but when I try to mysqldump these with --opt, the server crashes. E.g. mysql> CREATE DATABASE myinnotest; mysql> CREATE TABLE myinnotest.t (id INT) TYPE=InnoDB; $ mysqldump -uroot --opt myinnotest > myinnotest.sql mysqldump: Can't get CREATE TABLE for table `t` (Lost connection to MySQL server during query) I found the option which causes the crash is --lock-tables, all the others implied by --opt work fine, dumping MyISAM-only dbs works fine as well. I've read all the stuff in the server log about reporting a bug, and I'm willing to do that, however, I would assume that if this was a bug affecting everybody it would have been seen and fixed long before, so I guess my update from 4.0.15 to 4.0.21 has somehow caused this. I wanted to ask if somebody here has an idea on how I might fix the issue locally? Thanks for reading this far, below is some more system info, Thomas Installed mysql rpms ------------------------------------------------ $ rpm -qa | grep -i mysql mysqlcc-0.9.2-1mdk MySQL-server-4.0.21-0 MySQL-client-4.0.21-0 InnoDB config in /etc/my.cnf: ------------------------------------------------ # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = /var/lib/mysql/ innodb_data_file_path = ibdata1:10M:autoextend innodb_log_group_home_dir = /var/lib/mysql/ innodb_log_arch_dir = /var/lib/mysql/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 256M innodb_additional_mem_pool_size = 20M # Set .._log_file_size to 25 % of buffer pool size innodb_log_file_size = 64M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 Server output: ------------------------------------------------ [WHEN MYSQLDUMPing InnoDB tables WITH --lock-tables] InnoDB: Error: select_lock_type is 99999999 inside ::start_stmt()! 040924 11:44:32InnoDB: Assertion failure in thread 36874 in file ha_innodb.cc line 4581 [...] 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 [...] Number of processes running now: 0 040924 11:44:32 mysqld restarted 040924 11:44:32 Warning: Asked for 196608 thread stack, but got 126976 040924 11:44:32 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 3404981 InnoDB: Doing recovery: scanned up to log sequence number 0 3404981 InnoDB: Last MySQL binlog file position 0 737921, [...] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
