Description:
I have a MySQL server reporting that the table is full: On my machine according the docs I can have up to 64TB
Linux 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
MySQL is configured as innodb-file-per-table
From error log:
110413 14:07:59 [ERROR] /usr/sbin/mysqld: The table 'real_estate_photo' is full
110413 14:07:59 [ERROR] /usr/sbin/mysqld: The table 'real_estate_photo' is full
110413 14:07:59 [ERROR] /usr/sbin/mysqld: The table 'real_estate_photo' is full
110413 14:07:59 [ERROR] /usr/sbin/mysqld: The table 'real_estate_photo' is full
110413 14:07:59 [ERROR] /usr/sbin/mysqld: The table 'real_estate_photo' is full
The table is 17G in size -rw-rw---- 1 mysql mysql 17247252480 Apr 13 14:03 real_estate_photo.ibd
Table information:
Table Rows Data Index Total Fraction
real_estate_photo 33.96M 6.25G 9.59G 15.84G 1.54%
Table Fragmentation:
Table Data Size Data Free % Fragmented
real_estate_photo 6397.00MB 3.00MB 0.05%
MySQL variables:
| have_innodb | YES |
| ignore_builtin_innodb | OFF |
| innodb_adaptive_hash_index | ON |
| innodb_additional_mem_pool_size | 536870912 |
| innodb_autoextend_increment | 16 |
| innodb_autoinc_lock_mode | 1 |
| innodb_buffer_pool_size | 11811160064 |
| innodb_checksums | ON |
| innodb_commit_concurrency | 0 |
| innodb_concurrency_tickets | 500 |
| innodb_data_file_path | ibdata1:100M:autoextend |
| innodb_data_home_dir | /var/lib/mysql/innodb/ |
| innodb_doublewrite | ON |
| innodb_fast_shutdown | 1 |
| innodb_file_io_threads | 4 |
| innodb_file_per_table | ON |
| innodb_flush_log_at_trx_commit | 0 |
| innodb_flush_method | O_DSYNC |
| innodb_force_recovery | 0 |
| innodb_lock_wait_timeout | 50 |
| innodb_locks_unsafe_for_binlog | OFF |
| innodb_log_buffer_size | 33554432 |
| innodb_log_file_size | 67108864 |
| innodb_log_files_in_group | 2 |
| innodb_log_group_home_dir | /var/lib/mysql/innodb/ |
| innodb_max_dirty_pages_pct | 90 |
| innodb_max_purge_lag | 0 |
| innodb_mirrored_log_groups | 1 |
| innodb_open_files | 500 |
| innodb_rollback_on_timeout | ON |
| innodb_stats_on_metadata | ON |
| innodb_support_xa | OFF |
| innodb_sync_spin_loops | 20 |
| innodb_table_locks | ON |
| innodb_thread_concurrency | 16 |
| innodb_thread_sleep_delay | 10000 |
| innodb_use_legacy_cardinality_algorithm | ON |
Table decription:
describe real_estate_photo;
+------------+--------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+------------+--------------+------+-----+---------+----------------+
| id | int(11) | NO | PRI | NULL | auto_increment |
| uid | varchar(64) | YES | UNI | NULL | |
| mls_num | varchar(32) | NO | MUL | | |
| caption | varchar(48) | NO | | | |
| office | varchar(64) | NO | MUL | | |
| board | varchar(32) | NO | MUL | NULL | |
| photo | varchar(128) | NO | MUL | | |
| thumb | tinyint(1) | NO | | 0 | |
| sort_order | int(11) | NO | | NULL | |
| status | tinyint(1) | NO | | NULL | |
+------------+--------------+------+-----+---------+----------------+
I have tried to increase the ibdata file and add another but this does not fix this. i cannot find anyone else that has this issue or has had this issue.
How to repeat:
I cannot tell you how to reproduce this, as I have another server that has more rows and larger data set and it runs without issue. The only difference is it is not innodb file per table.
