Bug #6314 MySQL Crash

• Submitted: 29 Oct 2004 6:45
• Modified: 30 Nov 2004 15:52
• Reporter: Shkaeel Ahmad
• Status: No Feedback
• Category: MySQL Server
• Severity: S2 (Serious)
• Version: 4.0.14-nt
• OS: Windows (Windows 2000 Professional)
• CPU Architecture: Any

[29 Oct 2004 6:45] Shkaeel Ahmad

Description:
InnoDB: Operating system error number 33 in a file operation.

How to repeat:
Probably by connecting org.apache.commons.dbcp API Connector on java version 1.4.2_06.

Suggested fix:
I think the following situation must be handled properly where two processes have got access violation exception.

040830 16:22:10  InnoDB: Operating system error number 33 in a file operation.
InnoDB: See http://www.innodb.com/ibman.html for installation help.
InnoDB: Error number 33 means 'Domain error'.
InnoDB: See also section 13.2 at http://www.innodb.com/ibman.html
InnoDB: about operating system error numbers.
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'aio read'.
InnoDB: Cannot continue operation.

Looking at the documentation for windows error 33:
33 (ERROR_LOCK_VIOLATION) 
The process cannot access the file because another process has locked a portion of the file.

[29 Oct 2004 8:51] Heikki Tuuri

Hi!

Do you have a backup program or a virus checker running concurrently, and scanning ibdata files?

If yes, you should try to exclude the ibdata files and ib_logfiles from that tool.

Regards,

Heikki

[5 Sep 2007 13:30] MySQL Verification Team

see bug #9709