ok thanks, this mysql has got a replication slave...
On the slave the ibdata has got a size close to 15Go (ie the master's size is 22Go) have you got an idea about this ??? thanks 2007/10/29, Dan Nelson <[EMAIL PROTECTED]>: > > In the last episode (Oct 29), Thomas Raso said: > > 2007/10/29, Dan Nelson <[EMAIL PROTECTED]>: > > > In the last episode (Oct 29), Thomas Raso said: > > > > i don't understand the size of the ibdata7 > > > > > > > > -rw-rw---- 1 mysql mysql 2.0G Oct 29 15:18 ibdata1 > > > > -rw-rw---- 1 mysql mysql 2.0G Oct 29 15:17 ibdata2 > > > > -rw-rw---- 1 mysql mysql 2.0G Oct 29 15:17 ibdata3 > > > > -rw-rw---- 1 mysql mysql 2.0G Oct 29 15:08 ibdata4 > > > > -rw-rw---- 1 mysql mysql 2.0G Oct 29 15:17 ibdata5 > > > > -rw-rw---- 1 mysql mysql 2.0G Oct 29 15:17 ibdata6 > > > > -rw-rw---- 1 mysql mysql 22G Oct 29 15:18 ibdata7 > > > > > > > > the size of the databases is near 8Go. > > > > innodb_data_file_path = > ibdata1:2000M;ibdata2:2000M;ibdata3:2000M;ibdata4:2000M;ibdata5:2000M;ibdata6:2000M;ibdata7:500M:autoextend > > > > > > > > is anybody has got a documentation about this... > > > > > > It means you have (or had at one point in the past) 28GB worth of > > > InnoDB tables created. If you know you have only 8GB in use and > > > want to recover the space used by those ibdata files, you will need > > > to back up all your tables, delete the ibdata files, and restore > > > the tables. I recommend setting innodb_file_per_table=1 so each > > > table gets its own tablespace file. That way, when you delete a > > > table, the space is immediately returned back to the filesystem. > > > > > > http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html > > > http://dev.mysql.com/doc/refman/5.0/en/multiple-tablespaces.html > > > > There is no way whitout stopping mysql ? > > > > for information it is a version 4.1 > > Nope; the backup/delete/restart/restore procedure is the only way. > > -- > Dan Nelson > [EMAIL PROTECTED] >
