Mysql Error 124 From Storage Engine
Community Podcasts MySQL.com Downloads Documentation Section Menu: MySQL Forums :: MyISAM :: Got error 124 from storage engine New Topic Advanced Search Got error 124 from storage engine Posted by: Eric George () Date: February 16, 2010 12:44PM Ok, I've got issues. I'm getting the above error on insert to my database. It's MySQL 4.1.22 on a RedHat Enterprise 4.0 box. I'm using MyISAM tables. The table in question has about 19 million records and is part of a merge table with a much larger compressed archive table. This configuration has been working fine for years, with no recent changes. Despite this error on insertion, the insert appears to complete successfully - my row count goes up, I can query against it (the actual table, and the merge table) and get reasonable results, etc. If I run a check table on this table I get the following: +-----------------+-------+----------+---------------------------------------------------------------+ | Table | Op | Msg_type | Msg_text | +-----------------+-------+----------+---------------------------------------------------------------+ | my_db.my_active | check | error | Size of datafile is: 5184194948 Should be: 5184541472 | | my_db.my_active | check | error | Corrupt | +-----------------+-------+----------+---------------------------------------------------------------+ If I run a repair table against it, it will tell me it is repaired, and a subsequent check table returns that it's OK. But the same thing happens again on the next insert. So I tried dumping the table with mysqldump, and then rebuilding it from the dump. Again, the new table looks fine - but as soon as I attempt to insert, I get the same error again?? I found some reference to index size issues when googling this error message. The size of the MYI file on disk is about 824MB - much smaller then some others. There are 4 indexes on the table - one is an auto-increment primary key, two others are single column non-unique indexes, and one is a 3 column unique index involving two ints and a double. Navigate:Previous Message•Next Message Options:Reply•Quote Subject Views Written By Posted Got error 124 from storage engine 6674 Eric George 02/16/2010 12:44PM Re: Got error 124 from storage engine 2412 Rick James 02/18/2010 04:25PM Sorry, you can't reply to this topic. It has been closed. powered by phorum Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advanc
14:46 Reporter: Igor Simonov Email Updates: Status: Duplicate Impact on me: None Category:MySQL Server: Partitions Severity:S1 (Critical) Version:5.1.30, 5.1.34, 5.1.36 OS:Any (linux, windows) Assigned to: Assigned Account Tags: corruption Triage: Triaged: D2 (Serious) View Add Comment Files Developer Edit Submission View Progress Log Contributions [5 May 2009 7:14] Igor Simonov Description: Any SQL queries return error 124 when "load data concurrent infile" is working How to repeat: creating table TABLE time int(4) unsigned not null, describe varchar(18) not null, addit char(12) default null, key ix_describe(describe), key ix_addit(addit) engine=MyISAM partition by range http://forums.mysql.com/read.php?21,354376,354376 (time) (partition p0 values less then (600) engine = MyISAM, partition p1 values less then (1200) engine = MyISAM, partition p2 values less then (1800) engine = MyISAM, partition p3 values less then (2400) engine = MyISAM) inserting data load data concurrent infile '/home/igor/data.txt' into table database.TABLE; when the loading data any simple query like as "select * from database.TABLE" will return error 124. [5 https://bugs.mysql.com/bug.php?id=44657 May 2009 8:13] Igor Simonov query must be like select * from TABLE where describe='something'; error will be returned at the "load concurrent" starts creating indexes if query like select * from table limit 10; all ok. [5 May 2009 8:36] Sveta Smirnova Thank you for the report. I can not repeat described behavior with test data. Please provide your error log file. [5 May 2009 8:38] Sveta Smirnova Please also specify your operating system. [6 May 2009 12:41] Igor Simonov create table and load dataAttachment: create.sql (application/octet-stream, text), 706 bytes.
[6 May 2009 12:42] Igor Simonov error fileAttachment: mysql.local.err (application/octet-stream, text), 1.44 KiB. [6 May 2009 12:43] Igor Simonov mysqladmin variablesAttachment: mysqladmin.vari (application/octet-stream, text), 19.73 KiB. [6 May 2009 12:43] Igor Simonov configuration fileAttachment: my.cnf (application/octet-stream, text), 632 bytes. [6 May 2009 12:44] Igor Simonov mysql consoleAttachment: screen.txt (text/plain), 4.65 KiB. [6 May 2009 13:02] Igor Simonov tested OS Linux RHEL AS 4.6 x64, CentOS 5.3 x64 i am can not upload data file because it over 5M size. it file is a log of tcpdump converted by perl script. #!/usr/bin/perl while (Reporter: Shane Bester (Platinum Quality Contributor) Email Updates: Status: Closed Impact on me: None Category:MySQL Server: MyISAM storage engine Severity:S2 (Serious) Version:4.1,5.0,5.1 OS:Any (*) Assigned to: Sergey Vojtovich View Add Comment Files Developer https://bugs.mysql.com/bug.php?id=20357 Edit Submission View Progress Log Contributions [9 Jun 2006 13:07] Shane Bester Description: Queries using an index for MIN/MAX functions after an ALTER TABLE .. DISABLE KEYS statement return "Got error 124 from storage engine" until https://bugs.launchpad.net/bugs/885162 ALTER TABLE .. ENABLE KEYS is run. I tried 4.1BK, 5.0BK, 5.1BK, 5.0.21, 4.0.18 all giving same error. 4.0.27 Didn't show the error. Here's output of the testcase result that fails: .... mysql> ALTER TABLE `vhg` mysql error DISABLE KEYS; Query OK, 0 rows affected (0.00 sec) mysql> SELECT MAX(`id`) FROM `vhg`; ERROR 1030 (HY000): Got error 124 from storage engine mysql> ALTER TABLE `vhg` ENABLE KEYS; Query OK, 0 rows affected (0.00 sec) mysql> SELECT MAX(`id`) FROM `vhg`; +-----------+ | MAX(`id`) | +-----------+ | 1 | +-----------+ 1 row in set (0.00 sec) ... How to repeat: DROP TABLE IF EXISTS `vhg`; CREATE TABLE IF NOT EXISTS `vhg`(`id` TINYINT, mysql error 124 KEY(`id`))ENGINE=MyISAM; INSERT INTO `vhg`(`id`) VALUES (1); SELECT MAX(`id`) FROM `vhg`; ALTER TABLE `vhg` DISABLE KEYS; SELECT MAX(`id`) FROM `vhg`; ALTER TABLE `vhg` ENABLE KEYS; SELECT MAX(`id`) FROM `vhg`; Suggested fix: not sure. [16 Jun 2006 16:49] Bugs System A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/7771 [26 Jun 2006 10:57] Sergey Vojtovich Pushed into trees currently marked as 4.1.21, 5.0.23, 5.1.12. [26 Jun 2006 14:05] Jon Stephens Documented bugfix in 4.1.21/5.0.23/5.1.12 changelogs. Closed. [16 May 2007 15:47] Shane Bester 5.0.42 gives error 124 for this testcase: DROP TABLE IF EXISTS `vhg`; CREATE TABLE IF NOT EXISTS `vhg`(`id` TINYINT, KEY `r` (`id`))ENGINE=MyISAM; INSERT INTO `vhg`(`id`) VALUES (1),(2),(3),(4),(5); SELECT `id` FROM `vhg` FORCE INDEX (`r`) WHERE `id`=1; ALTER TABLE `vhg` DISABLE KEYS; SELECT `id` FROM `vhg` FORCE INDEX (`r`) WHERE `id`=1; ALTER TABLE `vhg` ENABLE KEYS; SELECT `id` FROM `vhg` FORCE INDEX (`r`) WHERE `id`=1; [16 May 2007 16:41] Shane Bester moving to a new bug report as this problem is not the same. Legal Policies Your Privacy Rights Terms of Use Contact Us Portions of this website are copyright © 2001, 2002 The PHP Group Page generated in 0.033 sec. using MySQ
person Affects Status Importance Assigned to Milestone Maria Edit Fix Released High Oleksandr "Sanja" Byelkin Edit Maria 5.3 You need to log in to change this bug's status. Affecting: Maria Filed here by: Philip Stoev When: 2011-11-02 Confirmed: 2011-11-02 Assigned: 2011-11-02 Started work: 2011-11-29 Completed: 2011-11-29 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Milestone Fix Released High Maria 5.3 Assigned to Me Oleksandr "Sanja" Byelkin (sanja-byelkin) Remote Watch None, the status of the bug is updated manually. None, the status of the bug is updated manually. URL: The information about this bug in Launchpad is automatically pulled daily from the remote bug. Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description When executing the following query: SELECT * FROM t1 WHERE t1.f1 IN ( SELECT 'k' UNION SELECT 'e' ) ; mysqld returned: ERROR 1030 (HY000): Got error 124 from storage engine backtrace: #0 my_error (nr=1030, MyFlags=0) at my_error.c:81 #1 0x083f34ef in handler::print_error (this=0xa7550990, error=124, errflag=0) at handler.cc:2981 #2 0x0833eb0f in report_error (table=0xa754fa18, error=124) at sql_select.cc:15468 #3 0x0833f549 in join_read_key2 (thd=0xaf82a20, tab=0xa7571840, table=0xa754fa18, table_ref=0xa757199c) at sql_select.cc:15731 #4 0x0833f3da in join_read_key (tab=0xa7571840) at sql_select.cc:15692 #5 0x0833e023 in sub_select (join=0xa7576490, join_tab=0xa7571840, end_of_records=false) at sql_select.cc:15129 #6 0x0833d8d0 in