The file ibdata1
is the system tablespace for the InnoDB infrastructure.
It contains several classes for information vital for InnoDB
- Table Data Pages
- Table Index Pages
- Data Dictionary
- MVCC Control Data
- Undo Space
- Rollback Segments
- Double Write Buffer (Pages Written in the Background to avoid OS caching)
- Insert Buffer (Changes to Secondary Indexes)
- Click Here to see a Pictorial Representation
You can separate Data and Index Pages from ibdata1
by enabling innodb_file_per_table. This will cause any newly created InnoDB table to store data and index pages in an external .ibd
file.
Example
- datadir is /var/lib/mysql
CREATE TABLE mydb.mytable (...) ENGINE=InnoDB;
, creates/var/lib/mysql/mydb/mytable.frm
- innodb_file_per_table enabled, Data/Index Pages Stored in
/var/lib/mysql/mydb/mytable.ibd
- innodb_file_per_table disabled, Data/Index Pages Stored in ibdata1
- innodb_file_per_table enabled, Data/Index Pages Stored in
No matter where the InnoDB table is stored, InnoDB's functionality requires looking for table metadata and storing and retrieving MVCC info to support ACID compliance and Transaction Isolation.
Here are my past articles on separating table data and indexes from ibdata1
Oct 29, 2010
: My Original Post in StackOverflowNov 26, 2011
: ERROR 1114 (HY000) at line 6308 in file & The table user_analysis is fullFeb 03, 2012
: Scheduled optimization of tables in MySQL InnoDBMar 25, 2012
: Why does InnoDB store all databases in one file?Apr 01, 2012
: Is innodb_file_per_table advisable?
WHAT TO DO NEXT
You can continue having ibdata1 stored everything, but that makes doing LVM snapshots real drudgery (my personal opinion).
You need to use My StackOverflow post and shrink that file permanently.
Please run this query:
SELECT
((POWER(1024,3)*94 - InnoDBDiskDataAndIndexes))/POWER(1024,3) SpaceToReclaim
FROM
(SELECT SUM(data_length+index_length) InnoDBDiskDataAndIndexes
FROM information_schema.tables WHERE engine='InnoDB') A;
This will tell how much wasted space can be reclaimed after applying the InnoDB Cleanup.