Provided by: mysql-utilities_1.6.4-1_all bug


       mysqldiskusage - Show Database Disk Usage


       mysqldiskusage [options] db ...


       This utility displays disk space usage for one or more databases. The utility optionally
       displays disk usage for the binary log, slow query log, error log, general query log,
       relay log, and InnoDB tablespaces. The default is to only show database disk usage.

       If the command-line lists no databases, the utility shows the disk space usage for all

       Sizes displayed without a unit indicator (such as MB) are in bytes.

       The utility determines the location of the data directory by requesting it from the
       server. For a local server, the utility obtains size information directly from files in
       the data directory and InnoDB home directory. In this case, you must have file system
       access to read those directories. Disk space usage shown includes the sum of all storage
       engine- specific files such as the .MYI and .MYD files for MyISAM and the tablespace files
       for InnoDB.

       If the file system read fails, or if the server is not local, the utility cannot determine
       exact file sizes. It is limited to information that can be obtained from the system
       tables, which therefore should be considered an estimate. For information read from the
       server, the account used to connect to the server must have the appropriate permissions to
       read any objects accessed during the operation.

       If information requested requires file system access but is not available that way, the
       utility prints a message that the information is not accessible. This occurs, for example,
       if you request log usage but the server is not local and the log files cannot be examined

       To specify how to display output, use one of the following values with the --format

       ·   grid (default)

           Display output in grid or table format like that of the mysql client command-line

       ·   csv

           Display output in comma-separated values format.

       ·   tab

           Display output in tab-separated format.

       ·   vertical

           Display output in single-column format like that of the \G command for the mysql
           client command-line tool.

       To turn off the headers for grid, csv, or tab display format, specify the --no-headers
       option.  OPTIONS.PP mysqldiskusage accepts the following command-line options:

       ·   --help

           Display a help message and exit.

       ·   --license

           Display license information and exit.

       ·   --all, -a

           Display all disk usage. This includes usage for databases, logs, and InnoDB

       ·   --binlog, -b

           Display binary log usage.

       ·   --empty, -m

           Include empty databases.

       ·   --format=<format>, -f<format>

           Specify the output display format. Permitted format values are grid, csv, tab, and
           vertical. The default is grid.

       ·   --innodb, -i

           Display InnoDB tablespace usage. This includes information about the shared InnoDB
           tablespace as well as .idb files for InnoDB tables with their own tablespace.

       ·   --logs, -l

           Display general query log, error log, and slow query log usage.

       ·   --no-headers, -h

           Do not display column headers. This option applies only for grid, csv, and tab output.

       ·   --quiet, -q

           Suppress informational messages.

       ·   --relaylog, -r

           Display relay log usage.

       ·   --server=<server>

           Connection information for the server.

           To connect to a server, it is necessary to specify connection parameters such as the
           user name, host name, password, and either a port or socket. MySQL Utilities provides
           a number of ways to supply this information. All of the methods require specifying
           your choice via a command-line option such as --server, --master, --slave, etc. The
           methods include the following in order of most secure to least secure.

           ·   Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example :

           ·   Use a configuration file (unencrypted, not visible) Note: available in
               release-1.5.0. Example : <configuration-file-path>[:<section>]

           ·   Specify the data on the command-line (unencrypted, visible). Example :

       ·   --ssl-ca

           The path to a file that contains a list of trusted SSL CAs.

       ·   --ssl-cert

           The name of the SSL certificate file to use for establishing a secure connection.

       ·   --ssl-cert

           The name of the SSL key file to use for establishing a secure connection.

       ·   --ssl

           Specifies if the server connection requires use of SSL. If an encrypted connection
           cannot be established, the connection attempt fails. Default setting is 0 (SSL not

       ·   --verbose, -v

           Specify how much information to display. Use this option multiple times to increase
           the amount of information. For example, -v = verbose, -vv = more verbose, -vvv =

       ·   --version

           Display version information and exit.

       For the --format option, the permitted values are not case sensitive. In addition, values
       may be specified as any unambiguous prefix of a valid value. For example, --format=g
       specifies the grid format. An error occurs if a prefix matches more than one valid value.
       NOTES.PP You must provide connection parameters (user, host, password, and so forth) for
       an account that has the appropriate privileges for all objects accessed during the

       The path to the MySQL client tools should be included in the PATH environment variable in
       order to use the authentication mechanism with login-paths. This will allow the utility to
       use the my_print_defaults tools which is required to read the login-path values from the
       login configuration file (.mylogin.cnf).  EXAMPLES.PP To show only the disk space usage
       for the employees and test databases in grid format (the default), use this command:

           shell> mysqldiskusage --server=root@localhost employees test
           # Source on localhost: ... connected.
           # Database totals:
           | db_name    |       total  |
           | employees  | 205,979,648  |
           | test       |       4,096  |
           Total database disk usage = 205,983,744 bytes or 196.00 MB

       To see all disk usage for the server in CSV format, use this command:

           shell> mysqldiskusage --server=root@localhost --format=csv -a -vv
           # Source on localhost: ... connected.
           # Database totals:
           Total database disk usage = 449,490,516 bytes or 428.00 MB
           # Log information.
           # The general_log is turned off on the server.
           # The slow_query_log is turned off on the server.
           # binary log information:
           Current binary log file = ./mysql-bin.000076
           Total size of binary logs = 168,399,105 bytes or 160.00 MB
           # Server is not an active slave - no relay log information.
           # InnoDB tablespace information:
           /data/ib_logfile0,5242880,log file,
           /data/ib_logfile1,5242880,log file,
           /data/ibdata1,220200960,shared tablespace,ibdata1:210M
           /data/ibdata2,10485760,shared tablespace,ibdata2:10M:autoextend
           /data/employees/departments.ibd,114688,file tablespace,
           /data/employees/dept_emp.ibd,30408704,file tablespace,
           /data/employees/dept_manager.ibd,131072,file tablespace,
           /data/employees/employees.ibd,23068672,file tablespace,
           /data/employees/salaries.ibd,146800640,file tablespace,
           /data/employees/titles.ibd,41943040,file tablespace,
           Total size of InnoDB files = 494,125,056 bytes or 471.00 MB

       PERMISSIONS REQUIRED.PP The user must have permissions to read the data directory or use
       an administrator, super user (sudo), or an account with elevated privileges to obtain
       access to the data directory.


       Copyright © 2006, 2016, Oracle and/or its affiliates. All rights reserved.

       This documentation is free software; you can redistribute it and/or modify it only under
       the terms of the GNU General Public License as published by the Free Software Foundation;
       version 2 of the License.

       This documentation is distributed in the hope that it will be useful, but WITHOUT ANY
       WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
       PURPOSE. See the GNU General Public License for more details.

       You should have received a copy of the GNU General Public License along with the program;
       if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
       Boston, MA 02110-1301 USA or see


       For more information, please refer to the MySQL Utilities and Fabric documentation, which
       is available online at


       Oracle Corporation (