Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 39.5Mb
PDF (A4) - 39.5Mb
PDF (RPM) - 38.7Mb
HTML Download (TGZ) - 11.0Mb
HTML Download (Zip) - 11.0Mb
HTML Download (RPM) - 9.7Mb
Man Pages (TGZ) - 217.2Kb
Man Pages (Zip) - 326.9Kb
Info (Gzip) - 3.6Mb
Info (Zip) - 3.6Mb
Excerpts from this Manual

B.4.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 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.