MySQL Forums
Forum List  »  General

MySQL/innodb database malfunctioning
Posted by: Nekrose DeCuir
Date: June 14, 2014 11:29PM

i play minecraft and i'm writing a database for an SQL interface mod for OpenComputers.

so.. this happens every time i set up my test server. which is twice now.

after creating "Minecraft" database, i import Users table.

i get this error:

#1813 - Tablespace for table '`minecraft`.`users`' exists. Please DISCARD the tablespace before IMPORT.

didn't do that the first time... but when i restarted it.. it wasn't able to be accessed.. so i had to remake it. anyway, the "Minecraft" name of the databse is there.. while the table Users is not.

this is what i get when i try to drop the db

2014-06-15 11:03:37 8324 [Note] Plugin 'FEDERATED' is disabled.
2014-06-15 11:03:37 1be4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-06-15 11:03:37 8324 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-06-15 11:03:37 8324 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-15 11:03:37 8324 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-06-15 11:03:37 8324 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-15 11:03:37 8324 [Note] InnoDB: Not using CPU crc32 instructions
2014-06-15 11:03:37 8324 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-06-15 11:03:37 8324 [Note] InnoDB: Completed initialization of buffer pool
2014-06-15 11:03:37 8324 [Note] InnoDB: Highest supported file format is Barracuda.
2014-06-15 11:03:37 8324 [Note] InnoDB: The log sequence numbers 1608234 and 1608234 in ibdata files do not match the log sequence number 1608350 in the ib_logfiles!
2014-06-15 11:03:37 8324 [Note] InnoDB: Database was not shutdown normally!
2014-06-15 11:03:37 8324 [Note] InnoDB: Starting crash recovery.
2014-06-15 11:03:37 8324 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-06-15 11:03:37 8324 [Note] InnoDB: Restoring possible half-written data pages 
2014-06-15 11:03:37 8324 [Note] InnoDB: from the doublewrite buffer...
2014-06-15 11:03:38 1be4  InnoDB: Error: table 'minecraft/users'
InnoDB: in InnoDB data dictionary has tablespace id 1,
InnoDB: but the tablespace with that id has name mysql/innodb_table_stats.
InnoDB: Have you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2014-06-15 11:03:38 8324 [Note] InnoDB: 128 rollback segment(s) are active.
2014-06-15 11:03:38 8324 [Note] InnoDB: Waiting for purge to start
2014-06-15 11:03:38 8324 [Note] InnoDB: 5.6.16 started; log sequence number 1608350
2014-06-15 11:03:38 8324 [Note] InnoDB: !!! innodb_force_recovery is set to 1 !!!
2014-06-15 11:03:38 8324 [Note] Server hostname (bind-address): '*'; port: 3306
2014-06-15 11:03:38 8324 [Note] IPv6 is available.
2014-06-15 11:03:38 8324 [Note]   - '::' resolves to '::';
2014-06-15 11:03:38 8324 [Note] Server socket created on IP: '::'.
2014-06-15 11:03:38 8324 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-06-15 11:03:38 8324 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2014-06-15 11:03:38 8324 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-06-15 11:03:38 8324 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-06-15 11:03:38 8324 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2014-06-15 11:03:38 8324 [Note] Event Scheduler: Loaded 0 events
2014-06-15 11:03:38 8324 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.16'  socket: ''  port: 3306  MySQL Community Server (GPL)
2014-06-15 11:03:47 8324 [ERROR] InnoDB: Failed to find tablespace for table '"minecraft"."users"' in the cache. Attempting to load the tablespace with space id 1.
2014-06-15 11:03:47 15f8  InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
2014-06-15 11:03:47 8324 [ERROR] InnoDB: Could not find a valid tablespace file for 'minecraft/users'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-06-15 11:03:47 8324 [Warning] InnoDB: Orphan table encountered during DROP DATABASE. This is possible if 'minecraft/users.frm' was lost.
2014-06-15 11:03:47 8324 [Warning] InnoDB: Missing minecraft/users.ibd file for table minecraft/users.
2014-06-15 11:03:47 15f8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-06-15 11:03:47 15f8  InnoDB: Assertion failure in thread 5624 in file fsp0fsp.cc line 3355
InnoDB: Failing assertion: xdes_mtr_get_bit(descr, XDES_FREE_BIT, header_page % FSP_EXTENT_SIZE, mtr) == FALSE
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
22:03:47 UTC - mysqld got exception 0x80000003 ;
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=16777216
read_buffer_size=262144
max_used_connections=2
max_threads=151
thread_count=2
connection_count=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133777 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xae40050
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...
288300    mysqld.exe!my_thread_name()
4c1d3d    mysqld.exe!my_mb_ctype_mb()
39bccf    mysqld.exe!murmur3_32()
3b4ca7    mysqld.exe!murmur3_32()
37b315    mysqld.exe!murmur3_32()
37b5c5    mysqld.exe!murmur3_32()
37b75d    mysqld.exe!murmur3_32()
3b99a1    mysqld.exe!murmur3_32()
3b9b4e    mysqld.exe!murmur3_32()
3b9cfc    mysqld.exe!murmur3_32()
3ba39d    mysqld.exe!murmur3_32()
34f566    mysqld.exe!murmur3_32()
350066    mysqld.exe!murmur3_32()
2b43d5    mysqld.exe!murmur3_32()
3a04c    mysqld.exe!?ha_end@@YAHXZ()
74496    mysqld.exe!?plugin_foreach_with_mask@@YA_NPAVTHD@@P6AD0PAUst_plugin_int@@PAX@ZHI2@Z()
3a077    mysqld.exe!?ha_drop_database@@YAXPAD@Z()
10e02e    mysqld.exe!?mysql_rm_db@@YA_NPAVTHD@@PAD_N2@Z()
6d3d7    mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()
6f36b    mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()
70107    mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()
70f9a    mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()
e3d49    mysqld.exe!?do_handle_one_connection@@YAXPAVTHD@@@Z()
e3ded    mysqld.exe!handle_one_connection()
433d5b    mysqld.exe!murmur3_32()
28e116    mysqld.exe!win_pthread_mutex_trylock()
4c5010    mysqld.exe!my_mb_ctype_mb()
4c509a    mysqld.exe!my_mb_ctype_mb()
7581338a    kernel32.dll!BaseThreadInitThunk()
776a9f72    ntdll.dll!RtlInitializeExceptionChain()
776a9f45    ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (ae46e58): DROP DATABASE `Minecraft`Connection ID (thread ID): 2
Status: 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.
2014-06-15 11:07:58 7044 [Note] Plugin 'FEDERATED' is disabled.
2014-06-15 11:07:58 23dc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-06-15 11:07:58 7044 [Note] InnoDB: Started in read only mode
2014-06-15 11:07:58 7044 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-06-15 11:07:58 7044 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-15 11:07:58 7044 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-06-15 11:07:58 7044 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-15 11:07:58 7044 [Note] InnoDB: Not using CPU crc32 instructions
2014-06-15 11:07:58 7044 [Note] InnoDB: Disabling background IO write threads.
2014-06-15 11:07:58 7044 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-06-15 11:07:58 7044 [Note] InnoDB: Completed initialization of buffer pool
2014-06-15 11:07:58 7044 [Note] InnoDB: Highest supported file format is Barracuda.
2014-06-15 11:07:58 7044 [Warning] InnoDB: Recovery skipped, --innodb-read-only set!
2014-06-15 11:07:58 7044 [Note] InnoDB: The log sequence numbers 1608234 and 1608234 in ibdata files do not match the log sequence number 1608360 in the ib_logfiles!
2014-06-15 11:07:58 7044 [ERROR] InnoDB: Can't initiate database recovery, running in read-only-mode.
2014-06-15 11:07:58 7044 [ERROR] Plugin 'InnoDB' init function returned error.
2014-06-15 11:07:58 7044 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2014-06-15 11:07:58 7044 [ERROR] Unknown/unsupported storage engine: InnoDB
2014-06-15 11:07:58 7044 [ERROR] Aborting

2014-06-15 11:07:58 7044 [Note] Binlog end
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'partition'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_METRICS'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_CMP'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'INNODB_TRX'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'BLACKHOLE'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'ARCHIVE'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'MRG_MYISAM'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'MyISAM'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'MEMORY'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'CSV'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'sha256_password'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'mysql_old_password'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'mysql_native_password'
2014-06-15 11:07:58 7044 [Note] Shutting down plugin 'binlog'
2014-06-15 11:07:58 7044 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2014-06-15 11:08:01 8720 [Note] Plugin 'FEDERATED' is disabled.
2014-06-15 11:08:01 21b0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-06-15 11:08:01 8720 [Note] InnoDB: Started in read only mode
2014-06-15 11:08:01 8720 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-06-15 11:08:01 8720 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-15 11:08:01 8720 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-06-15 11:08:01 8720 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-15 11:08:01 8720 [Note] InnoDB: Not using CPU crc32 instructions
2014-06-15 11:08:01 8720 [Note] InnoDB: Disabling background IO write threads.
2014-06-15 11:08:01 8720 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-06-15 11:08:01 8720 [Note] InnoDB: Completed initialization of buffer pool
2014-06-15 11:08:01 8720 [Note] InnoDB: Highest supported file format is Barracuda.
2014-06-15 11:08:01 8720 [Warning] InnoDB: Recovery skipped, --innodb-read-only set!
2014-06-15 11:08:01 8720 [Note] InnoDB: The log sequence numbers 1608234 and 1608234 in ibdata files do not match the log sequence number 1608360 in the ib_logfiles!
2014-06-15 11:08:01 8720 [ERROR] InnoDB: Can't initiate database recovery, running in read-only-mode.
2014-06-15 11:08:01 8720 [ERROR] Plugin 'InnoDB' init function returned error.
2014-06-15 11:08:01 8720 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2014-06-15 11:08:01 8720 [ERROR] Unknown/unsupported storage engine: InnoDB
2014-06-15 11:08:01 8720 [ERROR] Aborting

2014-06-15 11:08:01 8720 [Note] Binlog end
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'partition'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_METRICS'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_CMP'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'INNODB_TRX'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'BLACKHOLE'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'ARCHIVE'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'MRG_MYISAM'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'MyISAM'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'MEMORY'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'CSV'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'sha256_password'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'mysql_old_password'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'mysql_native_password'
2014-06-15 11:08:01 8720 [Note] Shutting down plugin 'binlog'
2014-06-15 11:08:01 8720 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2014-06-15 11:08:15 6620 [Note] Plugin 'FEDERATED' is disabled.
2014-06-15 11:08:15 1610 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-06-15 11:08:15 6620 [Note] InnoDB: Started in read only mode
2014-06-15 11:08:15 6620 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-06-15 11:08:15 6620 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-15 11:08:15 6620 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-06-15 11:08:15 6620 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-15 11:08:15 6620 [Note] InnoDB: Not using CPU crc32 instructions
2014-06-15 11:08:15 6620 [Note] InnoDB: Disabling background IO write threads.
2014-06-15 11:08:15 6620 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-06-15 11:08:15 6620 [Note] InnoDB: Completed initialization of buffer pool
2014-06-15 11:08:15 6620 [Note] InnoDB: Highest supported file format is Barracuda.
2014-06-15 11:08:15 6620 [Warning] InnoDB: Recovery skipped, --innodb-read-only set!
2014-06-15 11:08:15 6620 [Note] InnoDB: The log sequence numbers 1608234 and 1608234 in ibdata files do not match the log sequence number 1608360 in the ib_logfiles!
2014-06-15 11:08:15 6620 [ERROR] InnoDB: Can't initiate database recovery, running in read-only-mode.
2014-06-15 11:08:15 6620 [ERROR] Plugin 'InnoDB' init function returned error.
2014-06-15 11:08:15 6620 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2014-06-15 11:08:15 6620 [ERROR] Unknown/unsupported storage engine: InnoDB
2014-06-15 11:08:15 6620 [ERROR] Aborting

2014-06-15 11:08:15 6620 [Note] Binlog end
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'partition'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_METRICS'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_CMP'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'INNODB_TRX'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'BLACKHOLE'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'ARCHIVE'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'MRG_MYISAM'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'MyISAM'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'MEMORY'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'CSV'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'sha256_password'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'mysql_old_password'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'mysql_native_password'
2014-06-15 11:08:15 6620 [Note] Shutting down plugin 'binlog'
2014-06-15 11:08:15 6620 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2014-06-15 11:08:21 2536 [Note] Plugin 'FEDERATED' is disabled.
2014-06-15 11:08:21 1ca0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-06-15 11:08:21 2536 [Note] InnoDB: Started in read only mode
2014-06-15 11:08:21 2536 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-06-15 11:08:21 2536 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-15 11:08:21 2536 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-06-15 11:08:21 2536 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-15 11:08:21 2536 [Note] InnoDB: Not using CPU crc32 instructions
2014-06-15 11:08:21 2536 [Note] InnoDB: Disabling background IO write threads.
2014-06-15 11:08:21 2536 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-06-15 11:08:21 2536 [Note] InnoDB: Completed initialization of buffer pool
2014-06-15 11:08:21 2536 [Note] InnoDB: Highest supported file format is Barracuda.
2014-06-15 11:08:21 2536 [Warning] InnoDB: Recovery skipped, --innodb-read-only set!
2014-06-15 11:08:21 2536 [Note] InnoDB: The log sequence numbers 1608234 and 1608234 in ibdata files do not match the log sequence number 1608360 in the ib_logfiles!
2014-06-15 11:08:21 2536 [ERROR] InnoDB: Can't initiate database recovery, running in read-only-mode.
2014-06-15 11:08:21 2536 [ERROR] Plugin 'InnoDB' init function returned error.
2014-06-15 11:08:21 2536 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2014-06-15 11:08:21 2536 [ERROR] Unknown/unsupported storage engine: InnoDB
2014-06-15 11:08:21 2536 [ERROR] Aborting

2014-06-15 11:08:21 2536 [Note] Binlog end
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'partition'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_METRICS'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_CMP'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'INNODB_TRX'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'BLACKHOLE'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'ARCHIVE'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'MRG_MYISAM'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'MyISAM'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'MEMORY'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'CSV'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'sha256_password'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'mysql_old_password'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'mysql_native_password'
2014-06-15 11:08:21 2536 [Note] Shutting down plugin 'binlog'
2014-06-15 11:08:21 2536 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2014-06-15 11:10:29 7212 [Note] Plugin 'FEDERATED' is disabled.
2014-06-15 11:10:29 1d90 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-06-15 11:10:29 7212 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-06-15 11:10:29 7212 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-15 11:10:29 7212 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-06-15 11:10:29 7212 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-15 11:10:29 7212 [Note] InnoDB: Not using CPU crc32 instructions
2014-06-15 11:10:29 7212 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-06-15 11:10:29 7212 [Note] InnoDB: Completed initialization of buffer pool
2014-06-15 11:10:29 7212 [Note] InnoDB: Highest supported file format is Barracuda.
2014-06-15 11:10:29 7212 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1608360
2014-06-15 11:10:29 7212 [Note] InnoDB: Database was not shutdown normally!
2014-06-15 11:10:29 7212 [Note] InnoDB: Starting crash recovery.
2014-06-15 11:10:29 7212 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-06-15 11:10:29 7212 [Note] InnoDB: Restoring possible half-written data pages 
2014-06-15 11:10:29 7212 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1608487
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 8448
2014-06-15 11:10:29 7212 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2014-06-15 11:10:30 1d90  InnoDB: Rolling back trx with id 7938, 1 rows to undo
2014-06-15 11:10:30 7212 [Note] InnoDB: Rollback of trx with id 7938 completed
2014-06-15 11:10:30 1d90  InnoDB: Error: table 'minecraft/users'
InnoDB: in InnoDB data dictionary has tablespace id 1,
InnoDB: but the tablespace with that id has name mysql/innodb_table_stats.
InnoDB: Have you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2014-06-15 11:10:30 7212 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*320 pages, LSN=1608639
2014-06-15 11:10:30 7212 [Warning] InnoDB: Starting to delete and rewrite log files.
2014-06-15 11:10:30 7212 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2014-06-15 11:10:30 7212 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2014-06-15 11:10:30 7212 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2014-06-15 11:10:30 7212 [Warning] InnoDB: New log files created, LSN=1608639
2014-06-15 11:10:30 7212 [Note] InnoDB: 128 rollback segment(s) are active.
2014-06-15 11:10:30 7212 [Note] InnoDB: Waiting for purge to start
2014-06-15 11:10:30 7212 [Note] InnoDB: 5.6.16 started; log sequence number 1608487
2014-06-15 11:10:30 7212 [Note] Server hostname (bind-address): '*'; port: 3306
2014-06-15 11:10:30 7212 [Note] IPv6 is available.
2014-06-15 11:10:30 7212 [Note]   - '::' resolves to '::';
2014-06-15 11:10:30 7212 [Note] Server socket created on IP: '::'.
2014-06-15 11:10:30 7212 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-06-15 11:10:30 7212 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2014-06-15 11:10:30 7212 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-06-15 11:10:30 7212 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-06-15 11:10:30 7212 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2014-06-15 11:10:30 7212 [Note] Event Scheduler: Loaded 0 events
2014-06-15 11:10:30 7212 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.16'  socket: ''  port: 3306  MySQL Community Server (GPL)
2014-06-15 11:11:51 1f00  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.6/en/operating-system-error-codes.html
2014-06-15 11:11:51 7212 [ERROR] InnoDB: Cannot create file '.\minecraft\users.ibd'

2014-06-15 11:11:51 7212 [ERROR] InnoDB: The file '.\minecraft\users.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\minecraft\users.ibd' under the 'datadir' of MySQL.
2014-06-15 11:11:51 1f00  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.6/en/operating-system-error-codes.html
2014-06-15 11:11:51 7212 [ERROR] InnoDB: Cannot create file '.\minecraft\users.ibd'

2014-06-15 11:11:51 7212 [ERROR] InnoDB: The file '.\minecraft\users.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\minecraft\users.ibd' under the 'datadir' of MySQL.
2014-06-15 11:11:51 1f00  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.6/en/operating-system-error-codes.html
2014-06-15 11:11:51 7212 [ERROR] InnoDB: Cannot create file '.\minecraft\users.ibd'

2014-06-15 11:11:51 7212 [ERROR] InnoDB: The file '.\minecraft\users.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\minecraft\users.ibd' under the 'datadir' of MySQL.
2014-06-15 11:11:51 1f00  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.6/en/operating-system-error-codes.html
2014-06-15 11:11:51 7212 [ERROR] InnoDB: Cannot create file '.\minecraft\users.ibd'

2014-06-15 11:11:51 7212 [ERROR] InnoDB: The file '.\minecraft\users.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\minecraft\users.ibd' under the 'datadir' of MySQL.
2014-06-15 11:11:51 1f00  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.6/en/operating-system-error-codes.html
2014-06-15 11:11:51 7212 [ERROR] InnoDB: Cannot create file '.\minecraft\users.ibd'

2014-06-15 11:11:51 7212 [ERROR] InnoDB: The file '.\minecraft\users.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\minecraft\users.ibd' under the 'datadir' of MySQL.
2014-06-15 11:11:51 1f00  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.6/en/operating-system-error-codes.html
2014-06-15 11:11:51 7212 [ERROR] InnoDB: Cannot create file '.\minecraft\users.ibd'

2014-06-15 11:11:51 7212 [ERROR] InnoDB: The file '.\minecraft\users.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\minecraft\users.ibd' under the 'datadir' of MySQL.
2014-06-15 11:14:53 7212 [ERROR] InnoDB: Failed to find tablespace for table '"minecraft"."users"' in the cache. Attempting to load the tablespace with space id 1.
2014-06-15 11:14:53 1f00  InnoDB: Operating system error number 32 in a file operation.
InnoDB: The error means that another program is using InnoDB's files.
InnoDB: This might be a backup or antivirus software or another instance
InnoDB: of MySQL. Please close it to get rid of this error.
2014-06-15 11:14:53 7212 [ERROR] InnoDB: Could not find a valid tablespace file for 'minecraft/users'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-06-15 11:14:53 7212 [Warning] InnoDB: Orphan table encountered during DROP DATABASE. This is possible if 'minecraft/users.frm' was lost.
2014-06-15 11:14:53 7212 [Warning] InnoDB: Missing minecraft/users.ibd file for table minecraft/users.
2014-06-15 11:14:53 1f00 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-06-15 11:14:53 1f00  InnoDB: Assertion failure in thread 7936 in file fsp0fsp.cc line 3355
InnoDB: Failing assertion: xdes_mtr_get_bit(descr, XDES_FREE_BIT, header_page % FSP_EXTENT_SIZE, mtr) == FALSE
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
22:14:53 UTC - mysqld got exception 0x80000003 ;
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=16777216
read_buffer_size=262144
max_used_connections=2
max_threads=151
thread_count=2
connection_count=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133777 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xad24e48
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...
12c8300    mysqld.exe!my_thread_name()
1501d3d    mysqld.exe!my_mb_ctype_mb()
13dbccf    mysqld.exe!murmur3_32()
13f4ca7    mysqld.exe!murmur3_32()
13bb315    mysqld.exe!murmur3_32()
13bb5c5    mysqld.exe!murmur3_32()
13bb75d    mysqld.exe!murmur3_32()
13f99a1    mysqld.exe!murmur3_32()
13f9b4e    mysqld.exe!murmur3_32()
13f9cfc    mysqld.exe!murmur3_32()
13fa39d    mysqld.exe!murmur3_32()
138f566    mysqld.exe!murmur3_32()
1390066    mysqld.exe!murmur3_32()
12f43d5    mysqld.exe!murmur3_32()
107a04c    mysqld.exe!?ha_end@@YAHXZ()
10b4496    mysqld.exe!?plugin_foreach_with_mask@@YA_NPAVTHD@@P6AD0PAUst_plugin_int@@PAX@ZHI2@Z()
107a077    mysqld.exe!?ha_drop_database@@YAXPAD@Z()
114e02e    mysqld.exe!?mysql_rm_db@@YA_NPAVTHD@@PAD_N2@Z()
10ad3d7    mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()
10af36b    mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()
10b0107    mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()
10b0f9a    mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()
1123d49    mysqld.exe!?do_handle_one_connection@@YAXPAVTHD@@@Z()
1123ded    mysqld.exe!handle_one_connection()
1473d5b    mysqld.exe!murmur3_32()
12ce116    mysqld.exe!win_pthread_mutex_trylock()
1505010    mysqld.exe!my_mb_ctype_mb()
150509a    mysqld.exe!my_mb_ctype_mb()
7581338a    kernel32.dll!BaseThreadInitThunk()
776a9f72    ntdll.dll!RtlInitializeExceptionChain()
776a9f45    ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (ad3ce30): DROP DATABASE `Minecraft`Connection ID (thread ID): 38
Status: 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.

so, i tried to use the innodb_recovery = 1 (what ever it's called)... all the way up to 5.. nothing worked. it all just said "skipping recovery" in the logs.

the ONLY thing i did to the server was set lower_case_table_names = 2... as i always do.. on production servers and testing servers alike. and i've never had this happen... again, it's happened to both installations of this MySQL. installed the same version on my production server and it runs fine.

Windows Version: Windows 7 Ultimate SP1 64-bit
XAMPP Version: 1.8.3
Server version: 5.6.16 - MySQL

Options: ReplyQuote


Subject
Written By
Posted
MySQL/innodb database malfunctioning
June 14, 2014 11:29PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.