MySQL Bugs: #81668: while inserting data into database #1030

Bug #81668	while inserting data into database #1030 - Got error -1 from storage engine
Submitted:	1 Jun 2016 6:42	Modified:	1 Jun 2016 6:58
Reporter:	ajit rew	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	Distrib 5.5.37,	OS:	Ubuntu (12.04)
Assigned to:		CPU Architecture:	Any
Tags:	#1030 #-1 from storage engine #storage engine

Description:
I created one table users in mysql with two fields Name n ID
able to create table successfully while inserting query giving an prompt 

#1030 - Got error -1 from storage engine

both fields ID having INT type with length 10 and Name have varchar type with length 30

Wanted to data get inserted successfully.
But that not happening.

How to repeat:
Created another db with users table and tried to create twho columns name and firstname table created successfully but same problem show that  #1030 - Got error -1 from storage engine.
Both fields name and firstname are varchar data type and having length 30 respectively 

And While deleting the users table in db is shows #2013 - Lost connection to MySQL server during query as a prompt  

wanted to insert data but not letting me insert due to #1030 - Got error -1 from storage engine then i thought drop the created table n create new but not able to drop due to #2013 - Lost connection to MySQL server during query as a prompt   

Suggested fix:
wanted to insert data in the database
wanted to drop the database which is not necessary to me.

Thank you for taking the time to report a problem.  Unfortunately you are not using a current version of the product you reported a problem with -- the problem might already be fixed. Please download a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open" and attach reproducible test case so that we can reproduce this issue at our end.  Again, thank you for your continued support of MySQL.