Look at your my.cnf for a configuration directive called 'innodb_data_file_path'. This is where you configure the files for the innodb table space. The last one is probably an auto-grow. My guess is that every time it complains, it's just added 8MB to the file. If you remove the auto-grow (and I can't remember what the configuration name is for that.. sorry), and add another 2GB file, it should be fine. You'll want to keep an eye on it though, so you can add 2GB files more into the future. That is, unless you add the autogrow to the last file.
The mysql online docs have lots of good info on this. On 4/25/06, Todd Smith <[EMAIL PROTECTED]> wrote: > > Hello > > I have inherited an INNODB database. I am new to MySQL and may not be > describing my problem correctly so any suggestions or questions are > welcome. > I have data files named ib_data_00 through ib_data_14 all of which are > 2.0G. > I also have ib_data_15 which is 26G. I am receiving errors saying that > the > innodb space is full. I know that the space isn't full because it is > still > working. I am wondering how I can get a true size of the space used. I > would like to get back into the 2G segments. Any suggestions. > > Todd > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > >
