Bug #15450 | MySQL Freezes and acts extremely unstable with MyISAM storage type on Debian 64 | ||
---|---|---|---|
Submitted: | 2 Dec 2005 22:11 | Modified: | 5 Jan 2006 7:14 |
Reporter: | Ygor Lemos | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | mysql-4.1.15-max | OS: | Linux (Debian - 2.6.8-11-amd64-generic) |
Assigned to: | CPU Architecture: | Any |
[2 Dec 2005 22:11]
Ygor Lemos
[3 Dec 2005 17:19]
Valeriy Kravchuk
Thank you for a problem report. Weird behaviour (hangs and deadlocks) on Debian and x86_64 was reported many times. See, for example, http://bugs.mysql.com/bug.php?id=8555 and http://bugs.mysql.com/bug.php?id=7254. It was decided that the problem is caused by a bug in glibc for x86_64 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314408). Please, check that reports. I believe, you hit exactly the same problem.
[4 Dec 2005 22:02]
Ygor Lemos
Does this bug occours in MySQL 5.0 too? If i upgrade MySQL it will become fixed? As i see, there is no correction for this problem! The patch found in one of the Debian discuss list just doesn't work because it try to diff inexistent system files (NPTL).... I thnk that the other users wth this environment are with the same trouble to correct their DB problems.... Thanks Again, Ygor Lemos
[5 Dec 2005 7:14]
Valeriy Kravchuk
As I informed you, it looks like the real reason is the problem in some versions of glibc for x86_64, not in MySQL code itself. Please, inform about the version you are using.
[6 Jan 2006 0: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".