Bug #318 random table corruptions, mysql compiled with gcc 2.95
Submitted: 23 Apr 2003 12:28 Modified: 8 Feb 2005 19:42
Reporter: [ name withheld ] Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:4.0.12 OS:Linux (redhat 7.2/7.3)
Assigned to: CPU Architecture:Any

[23 Apr 2003 12:28] [ name withheld ]

I use mysql server 4.0.12 on redhat 7.2 and 7.3 compiled on another platform with gcc 2.95.3 199910030.

compile line:
CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro -felide-constructors -fno-exceptions -fno-rtti" \
./configure --prefix=/usr/local/$mysql_dir \
--enable-assembler --with-client-ldflags=-all-static --with-mysqld-ldflags=-all-static --with-extra-charsets=complex

I have random table corruptions, like this :
Can't open file: 'tablename.MYI'. (errno: 145)
SQL query like "REPAIR TABLE tablename;" fix the problem.

With mysql 3.23.54 compiled with same option on the platform gcc 2.95.3, it did not have this problem.


How to repeat:
[23 Apr 2003 12:42] Alexander Keremidarski
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

There is no How-To-Repeat
[22 May 2003 2:44] Michael Widenius
An additional note:

We would be very interested in finding a way to repeat this to know if this is a bug in MySQL or gcc.   Please consult the MySQL online manual in ow to make  a repeatable test case and open
this ticket again when you have managed to do that.
[8 Aug 2003 1:26] Lenz Grimmer
This one might be a duplicate of bug#563 - does it still happen with MySQL 4.0.14?
[25 Aug 2003 5:35] [ name withheld ]
According to our customers and us, it seems that there is no more this problem since mysql-4.0.14.  If in the future, there is new the same problem, I will answer here quickly.

[8 Feb 2005 19:42] Sergei Golubchik
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.