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:
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:
GNU's response to RH's stupidity