Bug #27503 mysq crashes when trying to drop database or even table
Submitted: 28 Mar 2007 16:27 Modified: 30 May 2007 7:19
Reporter: Roman Ovchinnikov Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:mysql Ver 14.12 Distrib 5.0.32, OS:Linux (Linux 2.6.18-3-amd64 (Debian))
Assigned to: Assigned Account CPU Architecture:Any

[28 Mar 2007 16:27] Roman Ovchinnikov
Description:
Mysql crashes when dropping table/database, same database works/drops fine on mysql  Ver 14.7 Distrib 4.1.11, for pc-linux-gnu (i386)

After failed drop we can see databasename/table.frm in mysql directory, and can't drop/create table until file databasename/table.frm is deleted by hand.

Some info about server/database:
amd64 2xOpteron 275 processors (dual core), 4gb ram, debian etch

Linux version 2.6.18-3-amd64 (Debian 2.6.18-7) (waldi@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 SMP Mon Dec 4 17:04:37 CET 2006

There are some records in log:
Mar 28 13:11:49 reklamist mysqld[7444]: InnoDB: ###### Diagnostic info printed to the standard error stream
Mar 28 13:11:49 reklamist mysqld[7444]: InnoDB: Error: semaphore wait has lasted > 600 seconds
Mar 28 13:11:49 reklamist mysqld[7444]: InnoDB: We intentionally crash the server, because it appears to be hung.
Mar 28 13:11:49 reklamist mysqld[7444]: 070328 13:11:49InnoDB: Assertion failure in thread 1132489056 in file srv0srv.c line 2093
Mar 28 13:11:49 reklamist mysqld[7444]: InnoDB: We intentionally generate a memory trap.
Mar 28 13:11:49 reklamist mysqld[7444]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Mar 28 13:11:49 reklamist mysqld[7444]: InnoDB: If you get repeated assertion failures or crashes, even
Mar 28 13:11:49 reklamist mysqld[7444]: InnoDB: immediately after the mysqld startup, there may be
Mar 28 13:11:49 reklamist mysqld[7444]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Mar 28 13:11:49 reklamist mysqld[7444]: InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
Mar 28 13:11:49 reklamist mysqld[7444]: InnoDB: about forcing recovery.
Mar 28 13:11:49 reklamist mysqld[7444]: mysqld got signal 11;
Mar 28 13:11:49 reklamist mysqld[7444]: This could be because you hit a bug. It is also possible that this binary
Mar 28 13:11:49 reklamist mysqld[7444]: or one of the libraries it was linked against is corrupt, improperly built,
Mar 28 13:11:49 reklamist mysqld[7444]: or misconfigured. This error can also be caused by malfunctioning hardware.
Mar 28 13:11:49 reklamist mysqld[7444]: We will try our best to scrape up some info that will hopefully help diagnose
Mar 28 13:11:49 reklamist mysqld[7444]: the problem, but since we have already crashed, something is definitely wrong
Mar 28 13:11:49 reklamist mysqld[7444]: and this may fail.
Mar 28 13:11:49 reklamist mysqld[7444]:
Mar 28 13:11:49 reklamist mysqld[7444]: key_buffer_size=268435456
Mar 28 13:11:49 reklamist mysqld[7444]: read_buffer_size=131072
Mar 28 13:11:49 reklamist mysqld[7444]: max_used_connections=4
Mar 28 13:11:49 reklamist mysqld[7444]: max_connections=100
Mar 28 13:11:49 reklamist mysqld[7444]: threads_connected=1
Mar 28 13:11:49 reklamist mysqld[7444]: It is possible that mysqld could use up to
Mar 28 13:11:49 reklamist mysqld[7444]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 479743 K
Mar 28 13:11:49 reklamist mysqld[7444]: bytes of memory
Mar 28 13:11:49 reklamist mysqld[7444]: Hope that's ok; if not, decrease some variables in the equation.
Mar 28 13:11:49 reklamist mysqld[7444]:
Mar 28 13:11:49 reklamist mysqld[7444]: thd=(nil)
Mar 28 13:11:49 reklamist mysqld[7444]: Attempting backtrace. You can use the following information to find out
Mar 28 13:11:49 reklamist mysqld[7444]: where mysqld died. If you see no messages after this, something went
Mar 28 13:11:49 reklamist mysqld[7444]: terribly wrong...
Mar 28 13:11:49 reklamist mysqld[7444]: frame pointer is NULL, did you compile with
Mar 28 13:11:49 reklamist mysqld[7444]: -fomit-frame-pointer? Aborting backtrace!
Mar 28 13:11:49 reklamist mysqld[7444]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Mar 28 13:11:49 reklamist mysqld[7444]: information that should help you find out what is causing the crash.
Mar 28 13:11:49 reklamist mysqld[7444]: InnoDB: Thread 1141287264 stopped in file btr0sea.c line 973
Mar 28 13:11:51 reklamist mysqld_safe[12462]: Number of processes running now: 0
Mar 28 13:11:51 reklamist mysqld_safe[12464]: restarted

my.cnf:

root@reklamist:/# grep -v \# /etc/mysql/my.cnf
[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock
[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0
[mysqld]
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /db/mysql-db
tmpdir          = /db/mysql-tmp
set-variable = tmp_table_size=10M
set-variable = table_cache=8192
language        = /usr/share/mysql/english
skip-external-locking
bind-address            = 192.168.0.217
key_buffer              = 256M
max_allowed_packet      = 32M
thread_stack            = 128K
thread_cache_size       = 8
query_cache_limit       = 1048576
query_cache_size        = 16777216
query_cache_type        = 1
skip-bdb
default-table-type=innodb

innodb_data_home_dir = /db/innodb
innodb_data_file_path = ibdata00:32768M;ibdata01:32768M;ibdata02:32768M;ibdata03:32768M;;ibdata04:32768M;
set-variable = innodb_log_file_size=512M
set-variable = innodb_log_buffer_size=32M
innodb_flush_log_at_trx_commit=0
set-variable = innodb_buffer_pool_size=896M
set-variable = innodb_additional_mem_pool_size=64M
set-variable = innodb_file_io_threads=8
set-variable = innodb_lock_wait_timeout=30
innodb_flush_method=O_DSYNC
set-variable = innodb_thread_concurrency=8

[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]

[isamchk]
key_buffer              = 16M

How to repeat:
try to drop table/database
[28 Mar 2007 17:02] Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version, 5.0.37. 

In case of the same problem, please, send the dump of that problematic database/table. Have you loaded it from dump on 5.0.32 or just installed new binaries?
[30 Mar 2007 10:17] Heikki Tuuri
Roman,

please attach the entire .err log to this report, gzipped.

Regards,

Heikki
[28 Apr 2007 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".
[30 May 2007 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".