Bug #62043 [ERROR] Got error 124 when reading table
Submitted: 1 Aug 2011 9:21 Modified: 19 Sep 2011 22:20
Reporter: Devang Modi Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:mysql-server-5.0.45-7.el5-x86_64 OS:Linux (RHEL Server release 5.3 (Tikanga))
Assigned to: CPU Architecture:Any
Tags: 124, error, Got, Reading, table, WHEN

[1 Aug 2011 9:21] Devang Modi
Dear Sir;
Suddenly without any previous notification or symptom on last 07-22-2011 at 9:07:05 AM MySQL log file was logged below error.

110722  9:07:05 [ERROR] Got error 124 when reading table './cvta0018/routedrawaccounting'

This is a dedicated database production , red hat enterprise based server, the server hardware is performing fine. Available Cpu , disk and memory is higher respect to requirement.
The said table in error message is belonging to MyISAM.
After occurrence of this error the table is perfect and fully readable.
But for precaution we ran "repair table" statement which completed without any error.

For your reference I am sharing mysql log file here with this mail.

Can you please tell us whether it is a bug or something else?


How to repeat:
Not know

Suggested fix:
[1 Aug 2011 10:19] Valeriy Kravchuk
Execute CHECK TABLE ... EXTENDED and/or myisamchk -e -vvv for that table. See http://dev.mysql.com/doc/refman/5.1/en/myisamchk-check-options.html for the details. 

Also I'd suggest to upgrade to recent 5.x.y (5.0.92 at least), as many bugs were fixed since 5.0.45.
[1 Aug 2011 17:20] Valeriy Kravchuk
Please, send the output of:

show create table routedrawaccounting\G
[2 Aug 2011 3:20] Devang Modi
Dear Sir;
Kindly find below the out of command that you suggested.

*************************** 1. row ***************************
       Table: routedrawaccounting
Create Table: CREATE TABLE `routedrawaccounting` (
  `recid` bigint(20) NOT NULL auto_increment,
  `clientlocid` bigint(20) NOT NULL default '0',
  `specificrouteid` bigint(20) NOT NULL default '0',
  `actspecificproductid` bigint(20) NOT NULL default '0',
  `type` char(2) NOT NULL default 'SD',
  `repspecificproductid` bigint(20) default NULL,
  `qtyissued` float default NULL,
  `qtysked` float default NULL,
  `qtyactual` float default NULL,
  `qtyretd` float default NULL,
  `qtyundelivered` float default NULL,
  `pricecodeid` bigint(20) default NULL,
  `recalc` char(1) NOT NULL default 'N',
  `editionid` bigint(20) NOT NULL default '2',
  PRIMARY KEY  (`recid`),
  KEY `clientlocid` (`clientlocid`,`specificrouteid`),
  KEY `recalc` (`recalc`),
  KEY `actspecificproductid` (`actspecificproductid`),
  KEY `repspecificproductid` (`repspecificproductid`),
  KEY `pricecodeid` (`pricecodeid`)


[6 Aug 2011 5:30] Sveta Smirnova
Thank you for the feedback.

Please upgrade to current version 5.0.92, try with it and if problem still exists try to find which query caused such an error. You can temporarily turn general logging on or use your application means.
[6 Sep 2011 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".
[7 Sep 2011 2:34] Devang Modi
Dear Sveta Smirnova;
After raising ticket with in week , we faced on hard drive failing issue,
i am assuming that because this failure, or hard drive degradation , such error prompt with NO further evidence.
Now, system is stable
What is your opinion on this?
[19 Sep 2011 22:20] Sveta Smirnova

thank you for the feedback. Disk failure can easily corrupt the table, therefore I suspect this is not MySQL bug and closing it as such.