Bug #27912 error 1030 "Got error 22 from storage engine [AGAIN!]
Submitted: 18 Apr 2007 4:42 Modified: 18 May 2007 6:38
Reporter: Jay Yoon Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Errors Severity:S3 (Non-critical)
Version:4.1.11 OS:Linux (redhat 3)
Assigned to: CPU Architecture:Any
Tags: 1030, error 1030, got error 22

[18 Apr 2007 4:42] Jay Yoon
Description:
hi. 
I sent a same question in last year.

---
i don't know this mean "Got error 22 from storage engine" 
i shew 127, 130 error number but i can not search number 22 

my working summary (mysql 4.1.11, os linux) 
- create new table 
- insert 140000 rows into new table 
- it's all 

it's normal process and have no problem until yesterday. 
but TODAY, this error is occured and inserting is stopped. 
---

mysql adviser has answered to my question. 
but The error is happening as ever. 

this is a my system. 
Filesystem Size Used Avail Use% Mounted on 
/dev/cciss/c0d0p3 66G 3.3G 60G 6% / 
/dev/cciss/c0d0p1 97M 15M 77M 16% /boot 
none 1004M 0 1004M 0% /dev/shm 

Filesystem Inodes IUsed IFree IUse% Mounted on 
/dev/cciss/c0d0p3 8749056 116583 8632473 2% / 
/dev/cciss/c0d0p1 25584 35 25549 1% /boot 
none 256934 1 256933 1% /dev/shm 

i think there is no problem. 

i will be able to solve this problem if i upgrade mysql version(now 4.1.11) to 5.0? 

thank you.

How to repeat:
error 1030 "Got error 22 from storage engine
[18 Apr 2007 6:38] Sveta Smirnova
Thank you for the report.

The bug system is place to report bugs in MySQL code. If cause of your problem is bug in MySQL code, we must know if it is repeatable with current version, because problem can be solved already. Therefore, please, upgrade to current version: limited supported 4.1.22 or full supported 5.0.37 and informa us about results.
[18 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".