Bug #27360 No documention for an innodb that has both autoextend set and a maximum size set
Submitted: 21 Mar 2007 21:40 Modified: 22 Mar 2007 5:16
Reporter: Dave Caroline Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5 OS:
Assigned to: CPU Architecture:Any

[21 Mar 2007 21:40] Dave Caroline 
Description:
A user on IRC asked about how to deal with a table full message, asked about his my.cnf setting this is what he had:

innodb_data_file_path = ibdata1:10M:autoextend:max:128M

The Table-Full page does not cover this particular situation

He backed up and removed the max:128M
it then worked
perhaps this needs adding to the Table-Full page

after any checking if this is in fact the valid fix

How to repeat:
use 
innodb_data_file_path = ibdata1:10M:autoextend:max:128M
in my.cnf and fill db

Suggested fix:
update docs for this situation
[21 Mar 2007 21:55] Paul DuBois 
Isn't this syntax covered in the section where you would
expect it, namely, the section on tablespace configuration
syntax?

http://dev.mysql.com/doc/refman/5.0/en/innodb-configuration.html
[22 Mar 2007 5:16] Valeriy Kravchuk 
Yes, I think, this page, http://dev.mysql.com/doc/refman/5.0/en/innodb-configuration.html, has all the information and links to solve this problem for InnoDB table(s).