The MySQL disk space full problem can be checked and solved through the following steps: 1. Check the usage of the data directory and locate databases or tables that occupy a large space; 2. Query the large table and analyze whether it is necessary to clean or archive, consider setting up TTL, archiving regularly or using partition tables; 3. Clean the binary logs, set up automatic cleaning strategies or manually clear old logs; 4. Process temporary files and slow query logs, and use logrotate for rotation compression; 5. Handle the problems of InnoDB table space not being recycled, uncleaned temporary tables and backup files, and regular monitoring and cleaning can effectively avoid disk fullness.
During the operation of MySQL database, the full disk space is a common problem, especially in systems with large amounts of data or untimely maintenance. This problem not only affects database performance, but also can cause service outages. The key to troubleshooting and solving such problems is to figure out who is occupying the space and how to clean or expand it.

Check the usage of MySQL data directory
First, to confirm the location of MySQL's data directory, you can usually view it through the following command:
mysql -u root -p -e "SHOW VARIABLES LIKE 'datadir';"
After getting the path, enter the directory and use du
command to view the size distribution of each database and file:

du -h /var/lib/mysql --max-depth=1
This step can help you quickly locate which database or table occupies a lot of space. If a database is obviously larger, you can further enter the database directory to view the specific table size.
View large and slow-growing tables
Enter MySQL, run the following SQL to query the tables with the largest footprint:

SELECT table_schema AS `Database`, table_name AS `Table`, round((data_length index_length) / 1024 / 1024, 2) `Size in MB` FROM information_schema.TABLES ORDER BY (data_length index_length) DESC LIMIT 10;
After finding the large tables, analyze whether these tables really need to retain so much data. For example, log tables, historical record tables, audit tables, etc. are often the "culprits".
If you find that some tables grow very fast, consider:
- Set TTL (Survival Time) to automatically clean old data
- Regularly archive data to other storage systems
- Use partition tables to slice by time for easy cleaning
Clean up binary logs (Binary Logs)
If the automatic cleaning policy is not set in MySQL, it will also occupy a lot of disk space.
You can view the current binlog settings through the following command:
SHOW VARIABLES LIKE 'expire_logs_days';
If the return value is 0, there is no automatic cleaning policy. It is recommended to set a reasonable number of days, such as 7 days:
SET GLOBAL expire_logs_days = 7;
At the same time, you can also manually clean old logs:
PURGE BINARY LOGS TO 'mysql-bin.010'; -- Clean until a file
Note: Before execution, make sure that these logs are no longer used for master-slave replication or recovery operations.
Temporary files and slow query logs may also take up space
MySQL sometimes generates temporary files, especially when performing large numbers of sorting, GROUP BY, or DISTINCT queries. These files are usually located in the system's temporary directory (such as /tmp
), but may also be configured in the data directory.
Additionally, space problems can also occur if slow query logs are enabled and log files are not rotated regularly. Check the path to the slow query log:
SHOW VARIABLES LIKE 'slow_query_log_file';
Consider using the logrotate tool to rotate and compress these logs to avoid unlimited growth.
Other common reasons and suggestions
- InnoDB tablespace not recycled : After data is deleted, InnoDB will not automatically free up disk space. You can consider using
OPTIMIZE TABLE
or rebuilding the table. - Uncleaned temporary tables : Check for unreleased temporary tables, especially large tables using the MEMORY engine.
- Remaining database backup files : Some automation scripts may store backup files in data directory, clean them regularly or change them to other locations.
Basically, these common investigation directions. Although not complicated, what is easy to ignore is log files and large table growth. As long as you monitor and set cleaning policies regularly, you can effectively avoid the problem of disk fullness.
The above is the detailed content of Troubleshooting MySQL Disk Space Fill-Up. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

When handling NULL values ??in MySQL, please note: 1. When designing the table, the key fields are set to NOTNULL, and optional fields are allowed NULL; 2. ISNULL or ISNOTNULL must be used with = or !=; 3. IFNULL or COALESCE functions can be used to replace the display default values; 4. Be cautious when using NULL values ??directly when inserting or updating, and pay attention to the data source and ORM framework processing methods. NULL represents an unknown value and does not equal any value, including itself. Therefore, be careful when querying, counting, and connecting tables to avoid missing data or logical errors. Rational use of functions and constraints can effectively reduce interference caused by NULL.

mysqldump is a common tool for performing logical backups of MySQL databases. It generates SQL files containing CREATE and INSERT statements to rebuild the database. 1. It does not back up the original file, but converts the database structure and content into portable SQL commands; 2. It is suitable for small databases or selective recovery, and is not suitable for fast recovery of TB-level data; 3. Common options include --single-transaction, --databases, --all-databases, --routines, etc.; 4. Use mysql command to import during recovery, and can turn off foreign key checks to improve speed; 5. It is recommended to test backup regularly, use compression, and automatic adjustment.

To view the size of the MySQL database and table, you can query the information_schema directly or use the command line tool. 1. Check the entire database size: Execute the SQL statement SELECTtable_schemaAS'Database',SUM(data_length index_length)/1024/1024AS'Size(MB)'FROMinformation_schema.tablesGROUPBYtable_schema; you can get the total size of all databases, or add WHERE conditions to limit the specific database; 2. Check the single table size: use SELECTta

GROUPBY is used to group data by field and perform aggregation operations, and HAVING is used to filter the results after grouping. For example, using GROUPBYcustomer_id can calculate the total consumption amount of each customer; using HAVING can filter out customers with a total consumption of more than 1,000. The non-aggregated fields after SELECT must appear in GROUPBY, and HAVING can be conditionally filtered using an alias or original expressions. Common techniques include counting the number of each group, grouping multiple fields, and filtering with multiple conditions.

Character set and sorting rules issues are common when cross-platform migration or multi-person development, resulting in garbled code or inconsistent query. There are three core solutions: First, check and unify the character set of database, table, and fields to utf8mb4, view through SHOWCREATEDATABASE/TABLE, and modify it with ALTER statement; second, specify the utf8mb4 character set when the client connects, and set it in connection parameters or execute SETNAMES; third, select the sorting rules reasonably, and recommend using utf8mb4_unicode_ci to ensure the accuracy of comparison and sorting, and specify or modify it through ALTER when building the library and table.

MySQL supports transaction processing, and uses the InnoDB storage engine to ensure data consistency and integrity. 1. Transactions are a set of SQL operations, either all succeed or all fail to roll back; 2. ACID attributes include atomicity, consistency, isolation and persistence; 3. The statements that manually control transactions are STARTTRANSACTION, COMMIT and ROLLBACK; 4. The four isolation levels include read not committed, read submitted, repeatable read and serialization; 5. Use transactions correctly to avoid long-term operation, turn off automatic commits, and reasonably handle locks and exceptions. Through these mechanisms, MySQL can achieve high reliability and concurrent control.

The most direct way to connect to MySQL database is to use the command line client. First enter the mysql-u username -p and enter the password correctly to enter the interactive interface; if you connect to the remote database, you need to add the -h parameter to specify the host address. Secondly, you can directly switch to a specific database or execute SQL files when logging in, such as mysql-u username-p database name or mysql-u username-p database name

The setting of character sets and collation rules in MySQL is crucial, affecting data storage, query efficiency and consistency. First, the character set determines the storable character range, such as utf8mb4 supports Chinese and emojis; the sorting rules control the character comparison method, such as utf8mb4_unicode_ci is case-sensitive, and utf8mb4_bin is binary comparison. Secondly, the character set can be set at multiple levels of server, database, table, and column. It is recommended to use utf8mb4 and utf8mb4_unicode_ci in a unified manner to avoid conflicts. Furthermore, the garbled code problem is often caused by inconsistent character sets of connections, storage or program terminals, and needs to be checked layer by layer and set uniformly. In addition, character sets should be specified when exporting and importing to prevent conversion errors
