MySQL Bin-log log too large causes disk full problem solved.

Today found the company monitoring system problems, check found that the original Bin-log log too large to cause the disk full, resulting in the inability to insert data. Then find a solution on the Internet.

1. Stop the library and delete the Bin-log log.

2. Perform reset master; (in the case of No library)

3. Execute Show binary logs;

Deletes the log before the specified bin-logs purge binary logs to 'MySQL-bin.000018 ';

The MySQL command line is stuck when a problem occurs during the operation of the Bin-log command. Finally restarted the database resolved.

After you delete the Bin-log log

Set global expire_logs_days = 10;
This is an order (only 10 days of Bin-log logs are reserved)
In or my.cnf plus expire_logs_days = 10

This article is from the "Li-Enlightened" blog, please make sure to keep this source http://jzzjw.blog.51cto.com/9921462/1717347

MySQL Bin-log log too large causes disk full problem solved.