MySQL Bugs: #23112: DB Backup through MySQL Administrator causes MySQL Server crash

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:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.024a	OS:	Windows (XP SP2)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	administrator, Backup, crash, DB, dump, MySQL

Description:
DB Backup through MySQL Administrator causes MySQL Server crash.

Event Type:	Error
Event Source:	MySQL
Event Category:	None
Event ID:	100
Date:		10/9/2006
Time:		11:35:07 AM
User:		N/A
Computer:	LAPTOP
Description:
Aborting

For more information, see Help and Support Center at http://www.mysql.com.  

Event Type:	Error
Event Source:	MySQL
Event Category:	None
Event ID:	100
Date:		10/9/2006
Time:		11:35:07 AM
User:		N/A
Computer:	LAPTOP
Description:
Do you already have another mysqld server running on port: 3306 ?

For more information, see Help and Support Center at http://www.mysql.com.  

No, i dont have another mysqld server running on port 3306.

Event Type:	Error
Event Source:	Application Error
Event Category:	(100)
Event ID:	1000
Date:		10/9/2006
Time:		11:33:08 AM
User:		N/A
Computer:	LAPTOP
Description:
Faulting application mysqld-nt.exe, version 0.0.0.0, faulting module mysqld-nt.exe, version 0.0.0.0, fault address 0x001d4015.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 6d 79 73   ure  mys
0018: 71 6c 64 2d 6e 74 2e 65   qld-nt.e
0020: 78 65 20 30 2e 30 2e 30   xe 0.0.0
0028: 2e 30 20 69 6e 20 6d 79   .0 in my
0030: 73 71 6c 64 2d 6e 74 2e   sqld-nt.
0038: 65 78 65 20 30 2e 30 2e   exe 0.0.
0040: 30 2e 30 20 61 74 20 6f   0.0 at o
0048: 66 66 73 65 74 20 30 30   ffset 00
0050: 31 64 34 30 31 35         1d4015  

How to repeat:
Perform a MySQL Backup through MySQL Administrator

Suggested fix:
Send me an iPod, and fix this bug please.

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.

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.

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.

Nope, its not in use by any other process.

Its a bug.

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.

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".