Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 39.3Mb
PDF (A4) - 39.4Mb
PDF (RPM) - 38.7Mb
HTML Download (TGZ) - 11.1Mb
HTML Download (Zip) - 11.1Mb
HTML Download (RPM) - 9.8Mb
Man Pages (TGZ) - 212.5Kb
Man Pages (Zip) - 321.5Kb
Info (Gzip) - 3.6Mb
Info (Zip) - 3.6Mb
Excerpts from this Manual

B.5.2.11 The table is full

If a table-full error occurs, it may be that the disk is full or that the table has reached its maximum size. The effective maximum table size for MySQL databases is usually determined by operating system constraints on file sizes, not by MySQL internal limits. See Section C.10.3, “Limits on Table Size”.


User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
  Posted by Stephen DeGabriele on July 16, 2012
I have been struggling with table is full errors for a while and have not found any answers.

Finally stumbled on the answer myself, it had to do with INNODB settings for the innodb_log_file_size and innodb_log_buffer_size

1) shutdown mysql
2) cd /var/lib/mysql
3) mkdir oldIblog
4) mv ib_logfile* oldIblog
5) edit /etc/my.cnf find the line innodb_log_file_size= and increase it to an appropriate value (I went to 1000MB as I am dealing with a very large dataset... 250million rows in one table). If you are not sure I suggest doubling the number every time you get a table is full error. I set innodb_log_buffer_size to 1/4 of the size of my log file and the problems went away.

Hope this helps others!

  Posted by Andrew Gray on April 10, 2017
We encountered a similar problem under Linux, where the datadir was mounted via NFS from a Netapp filer.
A SQL Load data command was failing with the error: Database 'LOAD' operation failed: The table 'volume_uid_age' is full
This database used InnoDB and innodb_file_per_table=1

In the filesystem we could see that the table (.ibd) was just under 2GB.

The problem was that the NFS mount was being performed with the option 'nfsvers=2'.
NFS v2 has a 2GB filesize limit.

Shutdown everything down, unmount the filesystem, change /etc/fstab to nfsvers=3, remount and restart.
Problem resolved.
Sign Up Login You must be logged in to post a comment.