Bug #6486 | Mysqldump crashes server instance | ||
---|---|---|---|
Submitted: | 7 Nov 2004 19:47 | Modified: | 29 Dec 2004 12:06 |
Reporter: | erik ludden | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Administrator | Severity: | S2 (Serious) |
Version: | 1.0.14 | OS: | Windows (Windows NT 4 sp6) |
Assigned to: | CPU Architecture: | Any |
[7 Nov 2004 19:47]
erik ludden
[7 Nov 2004 23:15]
erik ludden
In adddition to this bugreport: I discovered the cause of the error: there was an incomplete table in the database (MyIsam, only the .frm file existed, and probably corrupted) I can send the corrupted table if you want (it is very small), then you can reproduce it. However, the server should not crash on such a thing.
[7 Nov 2004 23:18]
erik ludden
drop this file in any MyIsam database folder and the server will crash on access
Attachment: variables.frm (application/octet-stream, text), 8.41 KiB.
[8 Nov 2004 16:01]
MySQL Verification Team
Yes plaease upload the table at: ftp://support.mysql.com/pub/mysql/upload and let know when done. Thanks
[9 Nov 2004 15:56]
erik ludden
Uploaded the file in question to ftp site supplied. The name is "variables.frm'
[29 Nov 2004 7:41]
Nicolai Reuschling
I do have the same problem: Since I migrated from v4.0.21 to v4.1.7 any run of mysqldump.exe results in an unusable OS (Windows Server 2003). mysqld consumes about 90% of CPU time. I have to reset the machine to resolve the problem.
[29 Nov 2004 12:06]
MySQL Verification Team
I tried to repeat but with not lucky the server launchs the below message: 041129 9:57:18 [ERROR] mysqld: Can't find file: 'variables.MYI' (errno: 2) 041129 10:00:21 [ERROR] mysqld: Can't find file: 'variables.MYI' (errno: 2) and the MA shows an error while doing the restore. So I need your instructions step by step for. Thanks in advance,
[14 Feb 2005 22:54]
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".