Bug #118506 innodb data files increased to max storage due to autoextend param provided in conf file
Submitted: 23 Jun 15:03
Reporter: PALANIVEL JAGANATHAN Email Updates:
Status: Open Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:8.0.26 OS:Linux
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: innodb

[23 Jun 15:03] PALANIVEL JAGANATHAN 
Description:
We have configured innodb data file path as follows
 
innodb_data_home_dir=/nsdata/nms/innodata1
innodb_data_file_path=nmsdata1:4000M;nmsdata2:4000M;nmsdata3:4000M;nmsdata4:4000M;nmsdata5:4000M;nmsdata6:4000M;nmsdata7:4000M;nmsdata8:4000M;nmsdata9:4000M;nmsdata10:4000M;nmsdata11:4000M;nmsdata12:4000M;nmsdata13:4000M;nmsdata14:4000M;nmsdata15:4000M;nmsdata16:4000M;nmsdata17:4000M;nmsdata18:4000M;nmsdata19:4000M;nmsdata20:4000M;nmsdata21:4000M;nmsdata22:4000M;nmsdata23:4000M;nmsdata24:4000M;nmsdata25:4000M;nmsdata26:4000M;nmsdata27:4000M;nmsdata28:4000M;nmsdata29:4000M;nmsdata30:4000M;nmsdata31:4000M;nmsdata32:4000M;nmsdata33:4000M;nmsdata34:4000M;nmsdata35:4000M;nmsdata36:4000M:autoextend

The datafile nmsdata36 increased to 280GB and it will increase hopefully. 

Can you provide an option to reclaim the innodb data storage space without affecting the data. 

How to repeat:
modify the my.cnf file and include the configuration as below 

innodb_data_home_dir=/nsdata/nms/innodata1
innodb_data_file_path=nmsdata1:4000M;nmsdata2:4000M;nmsdata3:4000M;nmsdata4:4000M;nmsdata5:4000M;nmsdata6:4000M;nmsdata7:4000M;nmsdata8:4000M;nmsdata9:4000M;nmsdata10:4000M;nmsdata11:4000M;nmsdata12:4000M;nmsdata13:4000M;nmsdata14:4000M;nmsdata15:4000M;nmsdata16:4000M;nmsdata17:4000M;nmsdata18:4000M;nmsdata19:4000M;nmsdata20:4000M;nmsdata21:4000M;nmsdata22:4000M;nmsdata23:4000M;nmsdata24:4000M;nmsdata25:4000M;nmsdata26:4000M;nmsdata27:4000M;nmsdata28:4000M;nmsdata29:4000M;nmsdata30:4000M;nmsdata31:4000M;nmsdata32:4000M;nmsdata33:4000M;nmsdata34:4000M;nmsdata35:4000M;nmsdata36:4000M:autoextend