090706 9:40:07 InnoDB: Error creating file '.\test\t1#p#p0#tmp#.ibd'. 090706 9:40:07 InnoDB: Operating system error number 80 in a file operation. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html InnoDB: The file already exists though the corresponding table did not InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB InnoDB: .ibd files around without using the SQL commands InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did InnoDB: mysqld crash in the middle of CREATE TABLE? You can InnoDB: resolve the problem by removing the file '.\test\t1#p#p0#tmp#.ibd' InnoDB: under the 'datadir' of MySQL. 090706 9:40:08 [Note] mysqld: Normal shutdown mysqld: missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "?func" 090706 9:40:10 InnoDB: Starting shutdown... 090706 9:40:17 InnoDB: Shutdown completed; log sequence number 0 41505137 090706 9:40:17 [Warning] Forcing shutdown of 1 plugins 090706 9:40:17 [Note] mysqld: Shutdown complete E:\builds\bzr\5.1\sql\debug>mysqld --console --skip-grant-tables --skip-name-resolve --innodb_buffer_pool_size=100M --innodb_flush_log_at_trx_commit=0 --innodb_lock_wait_timeout=1 --innodb_file_per_table --open-files-limit=2048 --innodb-checksums=0 --skip-innodb-doublewrite=1 090706 9:40:19 [Note] Plugin 'FEDERATED' is disabled. 090706 9:40:19 InnoDB: Started; log sequence number 0 41505137 090706 9:40:20 [Note] mysqld: ready for connections. Version: '5.1.37-debug' socket: '' port: 3306 Source distribution 090706 9:40:22 InnoDB: Error creating file '.\test\t1#p#p3#tmp#.ibd'. 090706 9:40:22 InnoDB: Operating system error number 80 in a file operation. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html InnoDB: The file already exists though the corresponding table did not InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB InnoDB: .ibd files around without using the SQL commands InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did InnoDB: mysqld crash in the middle of CREATE TABLE? You can InnoDB: resolve the problem by removing the file '.\test\t1#p#p3#tmp#.ibd' InnoDB: under the 'datadir' of MySQL. InnoDB: Error: trying to free a corrupt InnoDB: table handle. Magic n 26423527, magic n2 26423527, table name"test".090706 9:40:22 [ERROR] Invalid (old?) table or database name 't1#p#p0#tmp#' "#mysql50#t1#p#p0#tmp#" InnoDB: Apparent memory corruption: mem dump len 500; hex cdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd800000000000000000000000cdcdcdcd9268a520306576616c2e63003c0000000000000000000000000000000000000000000000480000000000000000000000480000004000000000000000cdcdcdc 000c00100000000000000000000300100004000000000000000cdcdcdcde7309301a07ea105a03ca1050100000000000000000000000000000000000000000000000104010000000000202020200400000001000000000000006082a105000000000000000070f80a0600000000000000000000000000000000a0d8a005a0d9a00500000000a078a10520202020202020204079a105050 0000000000000000000000000000000e730930120202020202020202020; asc h 0eval.c < H H @ P P h mysql.c U ` 0 0 ; InnoDB: Scanning backward trying to find previous allocated mem blocks Freed mem block at - 64, file mysql.c, line 597 Freed mem block at - 192, file 0eval.c, line 60 Freed mem block at - 1088, file mysql.c, line 597 Mem block at - 1344, file t0mem.c, line 47 Freed mem block at - 1600, file w0ins.c, line 82 Freed mem block at - 1856, file nodb.cc, line 3321 Freed mem block at - 2112, file w0ins.c, line 82 Freed mem block at - 2368, file nodb.cc, line 3321 Freed mem block at - 2624, file w0ins.c, line 82 Freed mem block at - 2880, file nodb.cc, line 3321 InnoDB: Scanning forward trying to find next allocated mem blocks Freed mem block at + 320, file m0rec.c, line 1129 Mem block at + 448, file t0mem.c, line 47 Freed mem block at + 832, file 0eval.c, line 60 Freed mem block at + 960, file 0pcur.c, line 29 Freed mem block at + 1216, file 0pcur.c, line 29 Freed mem block at + 1472, file mysql.c, line 597 Mem block at + 1728, file t0mem.c, line 242 Freed mem block at + 1984, file mysql.c, line 597 Freed mem block at + 2752, file w0ins.c, line 82 Freed mem block at + 3008, file mysql.c, line 1896 090706 9:40:22 InnoDB: Assertion failure in thread 2040 in file .\row\row0mysql.c line 700 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.1/en/forcing-recovery.html InnoDB: about forcing recovery. 090706 9:40:22 - mysqld got exception 0xc0000005 ; 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=1 max_threads=151 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337714 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x608e238 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... 00959E07 mysqld.exe!row_prebuilt_free()[row0mysql.c:700] 00947492 mysqld.exe!ha_innobase::close()[ha_innodb.cc:2666] 00460924 mysqld.exe!ha_partition::close()[ha_partition.cc:2587] 0076FF8D mysqld.exe!closefrm()[table.cc:1963] 0062BBE5 mysqld.exe!intern_close_table()[sql_base.cc:779] 0062BCFC mysqld.exe!free_cache_entry()[sql_base.cc:801] 00876307 mysqld.exe!my_hash_delete()[hash.c:529] 0062CE5E mysqld.exe!close_thread_table()[sql_base.cc:1386] 0062CCAC mysqld.exe!close_open_tables()[sql_base.cc:1195] 0062C9C7 mysqld.exe!close_thread_tables()[sql_base.cc:1347] 006B6C15 mysqld.exe!fast_alter_partition_table()[sql_partition.cc:6368] 007456D5 mysqld.exe!mysql_alter_table()[sql_table.cc:6905] 00698E41 mysqld.exe!mysql_execute_command()[sql_parse.cc:2860] 005F7230 mysqld.exe!sp_instr_stmt::exec_core()[sp_head.cc:2907] 005F64AA mysqld.exe!sp_lex_keeper::reset_lex_and_exec_core()[sp_head.cc:2735] 005F68BA mysqld.exe!sp_instr_stmt::execute()[sp_head.cc:2849] 005F1B71 mysqld.exe!sp_head::execute()[sp_head.cc:1253] 005F3B5A mysqld.exe!sp_head::execute_procedure()[sp_head.cc:1983] 0069C9F7 mysqld.exe!mysql_execute_command()[sql_parse.cc:4354] 006A1687 mysqld.exe!mysql_parse()[sql_parse.cc:5933] 0069586E mysqld.exe!dispatch_command()[sql_parse.cc:1213] 00694EE4 mysqld.exe!do_command()[sql_parse.cc:854] 007B5428 mysqld.exe!handle_one_connection()[sql_connect.cc:1127] 00888866 mysqld.exe!pthread_start()[my_winthread.c:85] 00A0AF71 mysqld.exe!_callthreadstart()[thread.c:293] 00A0AF17 mysqld.exe!_threadstart()[thread.c:277] 7D4E0017 kernel32.dll!FlsSetValue() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 060D3CA0=alter table `t1` add partition partitions 1 thd->thread_id=1 thd->killed=NOT_KILLED 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. InnoDB: Thread 7492 stopped in file .\os\os0sync.c line 271 InnoDB: Thread 6348 stopped in file .\os\os0sync.c line 574 InnoDB: Thread 2560 stopped in file .\sync\sync0arr.c line 337 E:\builds\bzr\5.1\sql\debug>