Bug #50608 mysqladmin variables "innodb_data_file_path" is truncated
Submitted: 25 Jan 2010 22:52 Modified: 26 Jan 2010 6:24
Reporter: Robin Bowes Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S2 (Serious)
Version:5.0.87 OS:Linux (CentOS 5.4 x86_64)
Assigned to: CPU Architecture:Any
Tags: mysqladmin variables show variables

[25 Jan 2010 22:52] Robin Bowes 
Description:
The entry for innodb_data_file_path is truncated in the output of both the "mysqladmin variables" and "mysql -e 'show variables'" commands.

I have 75 innodb data files, each 1000M in size. This is the entry in /etc/my.cnf:

innodb_data_file_path           = ibdata1:1000M;ibdata2:1000M;ibdata3:1000M;ibdata4:1000M;ibdata5:1000M;ibdata6:1000M;ibdata7:1000M;ibdata8:1000M;ibdata9:1000M;ibdata10:1000M;ibdata11:1000M;ibdata12:1000M;ibdata13:1000M;ibdata14:1000M;ibdata15:1000M;ibdata16:1000M;ibdata17:1000M;ibdata18:1000M;ibdata19:1000M;ibdata20:1000M;ibdata21:1000M;ibdata22:1000M;ibdata23:1000M;ibdata24:1000M;ibdata25:1000M;ibdata26:1000M;ibdata27:1000M;ibdata28:1000M;ibdata29:1000M;ibdata30:1000M;ibdata31:1000M;ibdata32:1000M;ibdata33:1000M;ibdata34:1000M;ibdata35:1000M;ibdata36:1000M;ibdata37:1000M;ibdata38:1000M;ibdata39:1000M;ibdata40:1000M;ibdata41:1000M;ibdata42:1000M;ibdata43:1000M;ibdata44:1000M;ibdata45:1000M;ibdata46:1000M;ibdata47:1000M;ibdata48:1000M;ibdata49:1000M;ibdata50:1000M;ibdata51:1000M;ibdata52:1000M;ibdata53:1000M;ibdata54:1000M;ibdata55:1000M;ibdata56:1000M;ibdata57:1000M;ibdata58:1000M;ibdata59:1000M;ibdata60:1000M;ibdata61:1000M;ibdata62:1000M;ibdata63:1000M;ibdata64:1000M;ibdata65:1000M;ibdata66:1000M;ibdata67:1000M;ibdata68:1000M;ibdata69:1000M;ibdata70:1000M;ibdata71:1000M;ibdata72:1000M;ibdata73:1000M;ibdata74:1000M;ibdata75:1000M

How to repeat:
Create a mysql config with a lot of innodb files (as per my config line).

Run the following commands:

"mysqladmin variables | grep innodb_data_file_path":

| innodb_data_file_path                   | ibdata1:1000M;ibdata2:1000M;ibdata3:1000M;ibdata4:1000M;ibdata5:1000M;ibdata6:1000M;ibdata7:1000M;ibdata8:1000M;ibdata9:1000M;ibdata10:1000M;ibdata11:1000M;ibdata12:1000M;ibdata13:1000M;ibdata14:1000M;ibdata15:1000M;ibdata16:1000M;ibdata17:1000M;ibdata18:1000M;ibdata19:1000M;ibdata20:1000M;ibdata21:1000M;ibdata22:1000M;ibdata23:1000M;ibdata24:1000M;ibdata25:1000M;ibdata26:1000M;ibdata27:1000M;ibdata28:1000M;ibdata29:1000M;ibdata30:1000M;ibdata31:1000M;ibdata32:1000M;ibdata33:1000M;ibdata34:1000M;ibdata35:10 |

"mysql -e 'show variables' | grep innodb_data_file_path":

innodb_data_file_path	ibdata1:1000M;ibdata2:1000M;ibdata3:1000M;ibdata4:1000M;ibdata5:1000M;ibdata6:1000M;ibdata7:1000M;ibdata8:1000M;ibdata9:1000M;ibdata10:1000M;ibdata11:1000M;ibdata12:1000M;ibdata13:1000M;ibdata14:1000M;ibdata15:1000M;ibdata16:1000M;ibdata17:1000M;ibdata18:1000M;ibdata19:1000M;ibdata20:1000M;ibdata21:1000M;ibdata22:1000M;ibdata23:1000M;ibdata24:1000M;ibdata25:1000M;ibdata26:1000M;ibdata27:1000M;ibdata28:1000M;ibdata29:1000M;ibdata30:1000M;ibdata31:1000M;ibdata32:1000M;ibdata33:1000M;ibdata34:1000M;ibdata35:10

You'll notice that the output is truncated.
[25 Jan 2010 23:05] Robin Bowes 
The reason this is an issue is that MySQL-zrm uses the output from "mysqladmin variables" to determine which ibdata files to backup.
[26 Jan 2010 6:24] Sveta Smirnova 
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #47973