table_name.ibd file size is increasing ( MySQL 5.7.7 Enterprise) ( Innodb Engines)
Now that you have posted the top tablespace file sizes, here is my attempt to answer your questions:


Yes, regardless of what value you have for innodb_file_per_table the files ibdata &amp; ib_logfile will be there. There can be multiple ibdata files depending on how you configure innodb_data_file_path. ib_logfile(s) can also be multiple depending on the value you use for innodb_log_files_in_group. To calculate how much size for log files is good for you, have a look at How to calculate a good innodb log file size


If your ib_logfiles are GBs, it will best to recalculate the size you really need (see link above) and set the size accordingly. ibdata* files are difficult to resize (the only way I know is to mysqldump the whole DB and reimport in a new installation).


You can calculate free tablespace that can be compacted by using this query:

SELECT table_name, (data_free)/power(1024,2) free_space_mb
FROM information_schema.tables
WHERE table_schema='[yourdb]'
ORDER BY free_space_mb DESC;


If you find any tables that have GBs worth of free space, then running OPTIMIZE on such tables should reduce the on-disk tablespace size.


If you have bigger disk/volume available that you want to take your datafiles to, use the following as a guide:


Stop MySQL service
Copy contents of your current data directory (usually /var/lib/mysql on CentOS/RHEL) to the new location
Make sure all folders and files on the new location where mysql files have been copied to, have owner AND group set to "mysql".
Edit /etc/my.cnf, set datadir to the new location where you copied mysql files to
Restart mysql service