Bug #23112 | DB Backup through MySQL Administrator causes MySQL Server crash | ||
---|---|---|---|
Submitted: | 9 Oct 2006 18:38 | Modified: | 10 Nov 2006 1:05 |
Reporter: | Jonathan Yaniv | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.024a | OS: | Windows (XP SP2) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | administrator, Backup, crash, DB, dump, MySQL |
[9 Oct 2006 18:38]
Jonathan Yaniv
[9 Oct 2006 22:49]
MySQL Verification Team
Thank you for the bug report. Please be sure that none MySQL server is running looking the task manager in the process tab (see for mysqld-nt.exe), then open a DOS prompt command screen and go to the \bin install directory and issue the below command i.e: mysqld-nt --defaults-file="C:\program files\Mysql\my.ini" --standalone --console change the path above for your actual my.ini path. Please paste here any message you will get during the server start or when it crashes. Thanks in advance.
[10 Oct 2006 0:20]
Jonathan Yaniv
C:\Documents and Settings\Owner.YOUR-8C087A2E17>mysqld-nt --defaults-file="C:\pr ogram files\mysql\MySQL Server 5.0\my.ini" --standalone --console 061009 17:19:33 InnoDB: Operating system error number 32 in a file operation. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html InnoDB: File name .\ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation.
[10 Oct 2006 0:44]
MySQL Verification Team
Thank you for the feedback. If you go to the URL suggested by the InnoDB engine you should see: # 32 (ERROR_SHARING_VIOLATION) The process cannot access the file because it is being used by another process. Then the server does an assert, possible causes: - There is another MySQL server already running using the same datadir. - There is another application like anti-virus, backup tool accesing the InnoDB files. Please verify.
[10 Oct 2006 0:54]
Jonathan Yaniv
Nope, its not in use by any other process. Its a bug.
[10 Oct 2006 1:05]
MySQL Verification Team
Thank you for the feedback. Could you please provide your my.ini file and the result of the dir command within the directory where the InnoDB files were created i.e: C:\mysql\data>dir O volume na unidade C não tem nome. O número de série do volume é C0FB-E588 Pasta de C:\mysql\data 08/10/2006 19:19 <DIR> . 08/10/2006 19:19 <DIR> .. 24/09/2006 14:56 <DIR> db5 02/10/2006 14:20 <DIR> ed2 27/09/2006 09:26 <DIR> gh 08/10/2006 19:19 18.874.368 ibdata1 08/10/2006 19:19 5.242.880 ib_logfile0 08/10/2006 18:29 5.242.880 ib_logfile1 02/10/2006 14:26 136 light-slow.log 02/10/2006 14:28 448 light.err 02/10/2006 14:28 1.213 light.log 01/10/2006 18:35 <DIR> mysql 28/09/2006 21:35 6 mysql_upgrade_info 24/09/2006 21:50 <DIR> report 05/10/2006 22:32 <DIR> test 7 arquivo(s) 29.361.931 bytes 8 pasta(s) 6.169.436.160 bytes disponíveis C:\mysql\data> Thanks in advance.
[11 Nov 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".