Bug #5600 Enabling autoextend option of innodb adds 'max:0M' at the end
Submitted: 15 Sep 2004 22:19 Modified: 20 Sep 2004 13:04
Reporter: Shuichi Tamagawa Email Updates:
Status: Closed Impact on me:
Category:MySQL Administrator Severity:S2 (Serious)
Version:1.0.12-GA OS:Microsoft Windows (Win XP / SP2)
Assigned to: Michael G. Zinner CPU Architecture:Any

[15 Sep 2004 22:19] Shuichi Tamagawa
If the 'Extend last file automatically' check box is checked in the innodb datafile parameter part of the 'Startup Variables' view, ':max:0M' is added at the end of the parameter in my.cnf file, which doesn't make sense. As a result, if you already have an innodb file which is bigger than the size specified in my.cnf file, mysql server can not startup after that.

How to repeat:
1.create innodb data file with autoextend option by editing my.cnf file.
2.start mysql server
3.make the innodb data file bigger than 10MB
4.from MySQL Administrator go to 'Startup Variables' -> 'Innodb Parameters' tab -> 'Datafiles' section
5.uncheck the 'Extend last file automatically' check box and check it again.
6.click 'Apply changes'
7.stop mysql server
8.start mysql server

If you open the my.cnf file you can see that the parameter has been changed.

Suggested fix:
Do not add ':max:' parameter if it is set 0M or 0k. 'Unlimited' may be used instead of '0'.
[20 Sep 2004 13:04] Michael G. Zinner
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at