How to fix ERROR 1114: Table is full in MySQL

MySQLINTERMEDIATEHIGHUpdated Dec 23, 2025· 210 views

This error indicates that MySQL cannot write to a table because it has reached its size limit or the disk is full. The fix depends on the underlying cause: insufficient disk space, InnoDB configuration limits, or MEMORY table size constraints.

Quick fix

Fixes ERROR 1114: Table is full

df -h /var/lib/mysql
  1. Check available disk space
  2. Free up disk space
  3. Verify MySQL can write again
  4. Check InnoDB configuration (if disk space was not the issue)
mysql — error
df -h /var/lib/mysql
ERROR 1114: Table is full

What this error means

ERROR 1114 occurs when MySQL attempts to write data to a table but cannot because the table has reached its maximum allowed size. This can happen for several reasons: the physical disk is completely full with no available space, the InnoDB tablespace has reached its configured maximum size limit, or a MEMORY table has exceeded its allowed size constraints. The error acts as a safeguard to prevent data corruption that could result from forced writes to full storage.

Typical symptoms

  • INSERT or UPDATE queries fail with "ERROR 1114: Table is full"
  • Database operations hang or timeout when writing data
  • Backup or bulk import operations fail partway through
  • Application cannot save new records to the database
  • Only writes fail while SELECT queries continue to work

Common causes

  1. Disk partition containing MySQL data is completely full with no free space
  2. InnoDB tablespace file has reached its configured maximum size limit (e.g., innodb_data_file_path with max constraint)
  3. MEMORY table exceeds max_heap_table_size or tmp_table_size configuration limits
  4. Large backup or import operation temporarily needs double disk space
  5. MyISAM table has exceeded the configured maximum row pointer size

How to fix "ERROR 1114: Table is full"

1Check available disk space

Start by checking how much free space is available on the partition containing your MySQL data directory.

On Linux/macOS:

bash
df -h /var/lib/mysql

On Windows (PowerShell):

powershell
Get-Volume | Where-Object {$_.DriveLetter -eq 'C'} | Select-Object SizeRemaining, Size

If the available space shows 0% or very close to it, disk space is the problem. You need to free up disk space before MySQL can write again.

2Free up disk space

If disk space is the issue, remove unnecessary files to make room:

1. Clear old MySQL binary logs (if binary logging is enabled):

bash
mysql -u root -p -e "SHOW BINARY LOGS;"
mysql -u root -p -e "PURGE BINARY LOGS BEFORE '2024-12-01';"

2. Remove old backup files:

bash
rm -f /var/backups/mysql-*.sql.gz

3. Clear temporary files in /tmp:

bash
rm -f /tmp/mysql*

4. Check and clean application logs:

bash
find /var/log -name "*.log" -type f -mtime +30 -delete

5. Consider expanding the partition if possible, or migrating MySQL data to a larger disk.

3Verify MySQL can write again

After freeing space, test that MySQL can write to the table:

bash
mysql -u root -p -e "USE yourdatabase; INSERT INTO testtable (column) VALUES ('test');"

If the INSERT succeeds, you have resolved the disk space issue.

4Check InnoDB configuration (if disk space was not the issue)

If you have adequate disk space but still get the error, check your InnoDB configuration:

bash
mysql -u root -p -e "SHOW VARIABLES LIKE 'innodb_data_file_path';"

If the output shows a max limit like:

bash
ibdata1:12M:autoextend:max:512M

The table has hit the configured maximum. You need to increase or remove the max limit.

5Increase InnoDB tablespace limit

Edit your MySQL configuration file (/etc/mysql/my.cnf or /etc/my.cnf):

Find the line with innodb_data_file_path and either:

Option A: Remove the max limit (recommended):

ini
[mysqld]
innodb_data_file_path = ibdata1:12M:autoextend

Option B: Increase the max limit:

ini
[mysqld]
innodb_data_file_path = ibdata1:12M:autoextend:max:2048M

Then restart MySQL:

bash
sudo systemctl restart mysql

Or on systems using mysqld_safe:

bash
sudo /usr/bin/mysqld_safe &

Verify the setting took effect:

bash
mysql -u root -p -e "SHOW VARIABLES LIKE 'innodb_data_file_path';"
6For MEMORY tables: check memory limits

If the error occurs on MEMORY (heap) tables, check the memory configuration:

bash
mysql -u root -p -e "SHOW VARIABLES LIKE 'max_heap_table_size'; SHOW VARIABLES LIKE 'tmp_table_size';"

To increase these limits, edit your MySQL configuration:

ini
[mysqld]
max_heap_table_size = 256M
tmp_table_size = 256M

Then restart MySQL and verify:

bash
sudo systemctl restart mysql
mysql -u root -p -e "SHOW VARIABLES LIKE 'max_heap_table_size';"

Advanced notes

For MyISAM tables, you can control the maximum table size via the MAX_ROWS option at table creation time or by adjusting myisam_data_pointer_size. By default, MyISAM tables can grow up to 256TB; this can be increased to 65,536TB if needed. If you are running MySQL in Docker, ensure your volume mount has sufficient space for your databases—Docker filesystem defaults can sometimes cause issues with tables exceeding 1GB. For very large tables, consider partitioning them across multiple tablespace files or implementing table partitioning to distribute data more efficiently.

Frequently asked questions

What does "ERROR 1114: Table is full" mean?
ERROR 1114 occurs when MySQL attempts to write data to a table but cannot because the table has reached its maximum allowed size. This can happen for several reasons: the physical disk is completely full with no available space, the InnoDB tablespace has reached its configured maximum size limit, or a MEMORY table has exceeded its allowed size constraints. The error acts as a safeguard to prevent data corruption that could result from forced writes to full storage.
How do I fix "ERROR 1114: Table is full"?
This error indicates that MySQL cannot write to a table because it has reached its size limit or the disk is full. The fix depends on the underlying cause: insufficient disk space, InnoDB configuration limits, or MEMORY table size constraints.
What causes "ERROR 1114: Table is full"?
Disk partition containing MySQL data is completely full with no free space InnoDB tablespace file has reached its configured maximum size limit (e.g., innodb_data_file_path with max constraint) MEMORY table exceeds max_heap_table_size or tmp_table_size configuration limits
Is the "ERROR 1114: Table is full" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading