Bug #68282 innodb_data_file_path Minimum Size in Documentation
Submitted: 6 Feb 2013 0:05 Modified: 3 Dec 2013 12:40
Reporter: Jervin R Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.6 OS:Any
Assigned to: Daniel Price

[6 Feb 2013 0:05] Jervin R

Documentation says K prefix and size is supported but InnoDB fails to start anyway.

2013-02-05 19:00:50 14540 [ERROR] InnoDB: syntax error in innodb_data_file_path
2013-02-05 19:00:50 14540 [ERROR] Plugin 'InnoDB' init function returned error.
2013-02-05 19:00:50 14540 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2013-02-05 19:00:50 14540 [ERROR] Unknown/unsupported storage engine: InnoDB
2013-02-05 19:00:50 14540 [ERROR] Aborting

How to repeat:
Start with:

Then restart with:

Suggested fix:
Update documentation if KB is not supported, otherwise emit in error log calculated values in K based on existing ibdata size or make sure K size is supported.
[6 Feb 2013 7:31] Erlend Dahl
Thanks for the bug report.

It is reproducible on 5.5 too. A brief look at the code seems to indicate that K was never supported in the first place.
[3 Dec 2013 12:40] Daniel Price
The reference manual has been updated to remove information about using KBs to specify the size for innodb_data_file_path.

Thank you for the bug report.
[8 Jan 2014 18:21] Daniel Price
Fixed as of 5.5.37, 5.6.17, 5.7.4, and here's the changelog entry:

"InnoDB" would fail to start when "innodb_data_file_path" specified the
data file size in kilobytes (KB) by appending "K" to the size value.

Thank you for the bug report.
[8 Jan 2014 18:25] Daniel Price
The previous changes to the reference manual have been reverted to reflect that specifying data file size in kilobytes is now supported as of 5.5.37, 5.6.17, and 5.7.4.
[27 Mar 2014 13:26] Laurynas Biveinis
5.5$ bzr log -r 4575
revno: 4575
committer: Aditya A <aditya.a@oracle.com>
branch nick: mysql-5.5
timestamp: Wed 2014-01-08 22:25:41 +0530
                  IN DOCUMENTATION
  The documentation says that we support 'K' prefix 
  while specifiying size for innodb datafile in the
  server variable for innodb_data_file_path ,but the
  function srv_parse_megabytes() only handles only 
  'M' (megabytes) and 'G' (gigabytes) .
  Modify srv_parse_megabytes() to handle Kilobytes. 
  Add in documentation that while specifying size 
  in KB it should be mentioned in multiples of 1024
  other wise they will be rounded off to nearest
  MB (megabyte) boundry .(eg if size mentioned
  as 2313KB will be considered as 2 MB ).
  [ Approved by Marko #rb 2387 ]