> -rw-rw---- 1 mysql mysql 1010M Aug 28 08:25 ibdata1
> -rw-rw---- 1 mysql mysql 264M Aug 27 17:09 awl.ibd
> -rw-rw---- 1 mysql mysql 112K Aug 28 08:25 bayes_expire.ibd
> -rw-rw---- 1 mysql mysql 96K Aug 27 17:09 bayes_global_vars.ibd
> -rw-rw---- 1 mysql mysql 468M Aug 27 21:11 bayes_seen.ibd
> -rw-rw---- 1 mysql mysql 148M Aug 27 21:43 bayes_token.ibd
> -rw-rw---- 1 mysql mysql 112K Aug 28 08:25 bayes_vars.ibd
> As you can see above, the new storage engine consumed 2 times
> bigger diskspace then the old. Is it a good behave or I should
> feel worried?
Nothing to worry. But you have perhaps imported your data twice and have
an empty ibdata1 file which only occupies space.
I quoted the innodb data files. Since you have defined
innodb_file_per_table, the table data is saved into the *.ibd files in
the database directory. Without that option all table data would go to
the ibdata* file(s) in the base data directory. As far as I know, data
for one table is saved either in ibdata* or in the *.ibd file, but not
both. Perhaps you played around and first imported the data without
innodb_file_per_table, which imported into ibdata1. Then you perhaps
dropped the tables and defined innodb_file_per table and imported again,
so the *.ibd files were created and filled. The ibdata1 may now be
empty, but it will never shrink.
Try the following: Dump all databases which have innodb tables and drop
all innodb tables. Stop the server, remove the ibdata1 and *.ibd files
and restart the server. An empty and small ibdata1 file will be
recreated. Now import your databases. I bet the ibdata1 file will not
grow and all data will be imported into *.ibd.
> It has exactly the same content like old database and it was
> simply injected from MySQL dump.
It is not neccessary to dump/reload the data for changing the database
engine of a table. Simply edit the tables with Mysql Query Browser or
the Mysql Administrator and change the table engine from myisam to
innodb. Or execute an SQL statement: "ALTER TABLE mytable ENGINE=innodb".
