| Bug #9153 | Crash - mysqld-nt.exe + ntdll.dll - v4.1.10 | ||
|---|---|---|---|
| Submitted: | 13 Mar 2005 5:44 | Modified: | 18 Mar 2005 14:56 |
| Reporter: | [ name withheld ] | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | v4.1.10 | OS: | Windows (Windows XP) |
| Assigned to: | CPU Architecture: | Any | |
[13 Mar 2005 5:44]
[ name withheld ]
[13 Mar 2005 5:59]
[ name withheld ]
The same crash happens, when I check or repair that database!
[13 Mar 2005 6:02]
[ name withheld ]
I found the table which caused the problem: prefix_users.frm All other files, like prefix_users.MYD, prefix_users.MYI are missing. I hope this can help to reproduce the bug.
[13 Mar 2005 6:04]
[ name withheld ]
Deleting the prefix_users.frm file, and recreating the table causes this crash: szAppName : mysqld-nt.exe szAppVer : 0.0.0.0 szModName : mysqld-nt.exe szModVer : 0.0.0.0 offset : 00128255
[13 Mar 2005 6:33]
[ name withheld ]
When I execute the following command
CREATE TABLE prefix_Users (
Username CHAR(50) NOT NULL,
Password CHAR(25) BINARY NOT NULL,
Email CHAR(75) NOT NULL,
Name CHAR(75),
Validation CHAR(20),
Status ENUM('Not Validated','Registered','Administrator') DEFAULT 'Registered' NOT NULL,
ReceiveMail ENUM('No','Yes') DEFAULT 'Yes' NOT NULL,
Newsletter ENUM('No','Yes') DEFAULT 'Yes' NOT NULL,
PRIMARY KEY (Username)
);
MySQL server crashes with this:
szAppName : mysqld-nt.exe szAppVer : 0.0.0.0 szModName : mysqld-nt.exe
szModVer : 0.0.0.0 offset : 00128255
Note, I do use the old password scheme, but I don't think that this is related to this bug.
[13 Mar 2005 8:20]
MySQL Verification Team
I wasn't able to repeat the crash creating the table mentioned. Could you please provide your my.ini file ? Thanks in advance.
[13 Mar 2005 18:10]
[ name withheld ]
I was able to track down the bug successfully. I had only 2 Mb free space on my drive I work on. So I checked the my.ini file, and found that default-storage-engine=INNODB is set, so will try to create at least 10 Mb innodb file in the data directory. Interesting, that knowing this, I made 12 Mb free space on that drive, and crash still continued. Maybe innodb needs 2x10 mb free space? Anyway, ignoring the default-storage-engine=INNODB resulted successful table creation. 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. I hope this will be enough info to track down these crashes. Thanks very much!
[18 Mar 2005 14:44]
[ name withheld ]
Any info, if this bug will be fixed in next release?
[18 Mar 2005 14:56]
MySQL Verification Team
Please read the Manua at: http://dev.mysql.com/doc/mysql/en/innodb.html for instructions how is handled the creation of InnoDB engine for data and log files.
