MySQL Bugs: #9281: Crash - mysqld-nt.exe + ntdll.dll

Bug #9281	Crash - mysqld-nt.exe + ntdll.dll - v4.1.10
Submitted:	18 Mar 2005 15:21	Modified:	23 Mar 2005 4:51
Reporter:	[ name withheld ]	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	v4.1.10	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any

Description:
szAppName : mysqld-nt.exe     szAppVer : 0.0.0.0     szModName : ntdll.dll     
szModVer : 5.1.2600.2180     offset : 00018fea

Miguel Solorzano did set my previous Bug #9153 as "Not a Bug" ...???

But as long this "feature" crashes MySQL v4.1.10, it *IS* a BUG!!!!!

I added enough data to track down & fix this bug.
Thanks!

How to repeat:
This crash always happens, when the my.ini file has
default-storage-engine=INNODB 
set, and there is NO enough free space available, for example less than 10 Mb.

Do a table creation, and MySQL crashes.

Suggested fix:
I think MySQL should check the available free space very careful, when database
creation, table creation, update, insert and similar space change resulting
statements are executed (especially for INNODB tables).

I was unable to reproduce this bug:

my HDD had 4KB left, and the following is what I got when I tried to reproduce this bug:

mysql> create table xxa (a int);
ERROR 14 (HY000): Can't change size of file (Errcode: 28)
mysql> exit
Bye

NOTE: I did use innodb as the default table type

Did you have the innodb 10 Mb file created already, or not?

You should try not to have this innodb file available on your mysql data partition, and have at least 1 Mb space. 
Fat32 partion was used.
Windows XP + SP2 was used, having latest updates.

Could you test in similar environment?
Thanks!

Bug confirmed -

Upgrading from 4.1 to 5.0 
Four servers went great, the fifth blew up

Results:
* Duplicate SERVICE was created (MYSQL 41 and MYSQL 5), they kept killing each other.
* As a result, the InnoDB tables CRASHED completely - had to recover them from a backup eventually
* Disabled the MySQL41 service
* Once I set the default table from InnoDB to MyISAM the crashes stopped (Thank god for this comment by the other user)

Windows 2003 - 2 GB memory - Raid 5 disk array - 120 GB free diskspace

If you need logs to do troubleshooting, feel free to email