MySQL Bugs: #10542: Stress: Server in deadlock state on Windows 2003.

Bug #10542	Stress: Server in deadlock state on Windows 2003.
Submitted:	11 May 2005 11:38	Modified:	22 Jul 2005 11:16
Reporter:	Disha	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.5 Beta	OS:	Any (Any)
Assigned to:		CPU Architecture:	Any

Description:
The server enters a deadlock state where multiple processes are waiting for the same resource. The test files used in these runs are the same that were used during functional testing and hence none of these test files actually lock a resource indefinetly.

This might be a build specific issue to 5.0.5.

How to repeat:
1) Run stress with multiple clients hitting the same server.

Find attached the following attachments:
For windows: (win_deadlocked.rar)
1) Processlist.txt: This includes the processes running/locked in mysql.
2) ping.txt: The server was alive.
3) taskmanager.jpg: The Page file kept increasing all the time.  
4) MYSQLWIN2.err
5) Master-Status_log-20050511.log: Server status and memory utilization.

As far as I can understood from mysqlwin2.err You did't have free disk space for continue:

050511 11:56:12 [ERROR] c:\\mysql\\bin\mysqld.exe: Disk is full writing '.\test\tb3.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
050511 11:57:16 [ERROR] c:\\mysql\\bin\mysqld.exe: Disk is full writing '.\test\tb4.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
050511 11:58:56  InnoDB: Encountered a problem with file .\ibdata1
050511 11:58:56  InnoDB: Disk is full. Try to clean the disk to free space.

Did you have enough free space on disk ?

Hi,
There was sufficient disk space. Im not sure why the error logs state otherwise.

Could you please repeat your stress tests without sufficient disk space ?

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