Corrupted MySQL Tables

cli_man · 10-22-2003, 04:42 AM

I have a Redhat 7.2 machine running MySQL 4.0.14 Just in the last week we have had problems with it getting corrupt tables, it seems to be getting about 1 corrupt table per 2 days, not the same time or anything.

This machine hosts about 60 other databases that have not had a single problem yet, this one is probably the most used but others on the system come pretty close on use.

Would anyone have an idea as to what might be causing this?

Here is an excerp from the mysql .err log

Code:

031015 12:50:11  mysqld started
031015 12:50:16  InnoDB: Started
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.0.14-standard'  socket: '/tmp/mysql.sock'  port: 3306
031016  9:34:20  read_key: Got error 127 when reading table './database/Users'
031016  9:34:20  read_key: Got error 127 when reading table './database/Users'
031016  9:35:04  read_key: Got error 127 when reading table './database/Users'
031016  9:35:04  read_key: Got error 127 when reading table './database/Users'
031016  9:40:23  read_key: Got error 127 when reading table './database/Users'
031016  9:41:03  read_key: Got error 127 when reading table './database/Users'
031016  9:41:07  read_key: Got error 127 when reading table './database/Users'
031016  9:41:19  read_key: Got error 127 when reading table './database/Users'
031016  9:41:28  read_const: Got error 127 when reading table ./database/Users
031016  9:41:36  read_const: Got error 127 when reading table ./database/Users
031016  9:43:40  Note: Found 124 of 125 rows when repairing './database/Users'
031020 14:45:19  Note: Found 2324 of 2325 rows when repairing './database/Bodies_r'
031021 17:43:01  Note: Found 244 of 245 rows when repairing './database/Bodies_m'
root@server:/usr/local/mysql/data$

This database also has several scripts that run almost continusly selecting and inserting data into them via the web and also a perl script.

verbal · 10-22-2003, 06:28 AM

Quote:

Originally posted by cli_man
I have a Redhat 7.2 machine running MySQL 4.0.14 Just in the last week we have had problems with it getting corrupt tables, it seems to be getting about 1 corrupt table per 2 days, not the same time or anything.

This is an "informed" guess...but a guess all the same: do you still have gcc 2.96 installed, and did you compile the installations yourself, or worse, did you use a pre-compiled *.rpm for installation from that era?

The 2.96 compiler was a broken one, it was actually based on a developer's snap shot of the upcoming 3.0 release at the time, (RH kind of PO'd gcc at the time rather effectivly over this).

Point here is that MySQL reported that spontaneously corrupted tables were a symptom experienced by databases which were compiled with this compiler. The quote on their site at the time was that they didn't know why it happened, but that they could repeat the problem only by compiling with 2.96. Their suggestion was not to use it. This is one reason I never use *.rpm's, you never know what someone used to compile the code with.

heres some notes on the topic:

this quote from MySQL:

Quote:

Compiler Advisory: Several users have reported random crashes and table corruptions when using MySQL binaries compiled with gcc 2.96 on the x86 Linux platform. We suggest that you use gcc 2.95 or gcc 2.91 to compile your own binaries. It should also be safe to use gcc 3.2.

can be found here:
http://www.mysql.com/downloads/mysql-3.23.html

GNU's response to RH's stupidity
http://gcc.gnu.org/gcc-2.96.html

Verbal

cli_man · 10-22-2003, 06:37 AM

No I used the precompiled binarys from mysql.com and I didn't use rpm's, I just grabbed their latest stable version at the time and installed it. Also it has been running for a couple months with no problem.

verbal · 10-22-2003, 06:44 AM

Quote:

Originally posted by cli_man
Also it has been running for a couple months with no problem.

This wouldn't matter.... the issue was described as "spontaneous"... it occured after a long period of normal use. The fact that you had gotten a couple months use was what made me think of the issue, you had described it perfectly.

BUT... if you got the binaries from them it is probably not the issue, sorry I wasn't of more help

good luck

Verbal

cli_man · 10-22-2003, 06:49 AM

Well thank you for trying.

Any other suggestions from anyone?

Also another one to through into the mix, I wonder if maybe a bad perl or php script might have something to do with it, is it possible to have a script corrupt a mysql table? Or is that pretty much impossible as MySQL would just give the script back an error and keep chugging along?