MySQL Bugs: #64145: Got error -1 from storage engine.

Bug #64145	Got error -1 from storage engine.
Submitted:	27 Jan 2012 10:01	Modified:	16 Jul 2013 13:20
Reporter:	shailu p	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.6	OS:	Linux (OpenSuse)
Assigned to:		CPU Architecture:	Any

Description:
I am having 4 databases on my machine, they all are working well but suddenly 2 days before when i was selecting data from one of my table from one of the databases, i got error in my error file "Incorrect information in table". After that i try to repair that table but it gives me error "Got error -1 from storage engine".
         I tried CHECK, REPAIR utilities but didn't succeed. After that i removed ibdata1, ib_logfile1 and ib_logfile0 files from my mysql directory and dropped my databases.After that i again restore my databases but during restoring of databases i observer that it successfully reloaded MyISAM tables but it hangs on InnoDB table.

What can i do to overcome this situation. Please help.

How to repeat:
There is no way to repeat this bug as it occurs due to unexpectedly reasons. I am sorry.

Please, upload the entire error log from your server (compressed if it is big), to begin with...

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".

I´ve the same problem as described above.

I´m sometimes get the "Got error -1 from storage engine", but there is no way to repeat this bug because it apperas accidentally.

Using MySQL 5.6.10 on Debian Squeeze

Here´s the MySQL error logfile but this seems ok:

130331 00:01:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2013-03-31 00:01:32 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-03-31 00:01:33 2055 [Note] Plugin 'FEDERATED' is disabled.
2013-03-31 00:01:33 7f1c826d5720 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.
2013-03-31 00:01:33 2055 [Note] InnoDB: The InnoDB memory heap is disabled
2013-03-31 00:01:33 2055 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2013-03-31 00:01:33 2055 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-03-31 00:01:33 2055 [Note] InnoDB: CPU does not support crc32 instructions
2013-03-31 00:01:33 2055 [Note] InnoDB: Using Linux native AIO
2013-03-31 00:01:33 2055 [Note] InnoDB: Initializing buffer pool, size = 6.0G
2013-03-31 00:01:33 2055 [Note] InnoDB: Completed initialization of buffer pool
2013-03-31 00:01:33 2055 [Note] InnoDB: Highest supported file format is Barracuda.
2013-03-31 00:01:35 2055 [Note] InnoDB: 128 rollback segment(s) are active.
2013-03-31 00:01:35 2055 [Note] InnoDB: Waiting for purge to start
2013-03-31 00:01:35 2055 [Note] InnoDB: 1.2.10 started; log sequence number 31050205481
2013-03-31 00:01:36 2055 [Note] Server hostname (bind-address): '*'; port: 3306
2013-03-31 00:01:36 2055 [Note] IPv6 is available.
2013-03-31 00:01:36 2055 [Note]   - '::' resolves to '::';
2013-03-31 00:01:36 2055 [Note] Server socket created on IP: '::'.
2013-03-31 00:01:36 2055 [Note] Event Scheduler: Loaded 0 events
2013-03-31 00:01:36 2055 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.10-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)

Closing as duplicate of bug #68722 (should be opposite way, but no big deal)