binlog及errorlog分区写满后mysql的行为

The observed output was.

• An error message was written to the MySQL error log. See below.
• Application throughput dropped, but did not stop.
• Binary logs stopped occuring.
• MySQL proactively stopped logging but continued to process transactions.

The end result was:

• The error log was ultimately truncated after reboot, so if the information was not captured while this was in action, this important messages would be lost.
• The primary slave used for read scalability and the secondary slave used for backups are now unusable.
• The backup and recovery process using slaves and point in time recovery via binary logs is not unusable.
• The three backup methods in use for the client are ineffective. It was necessary to disable access to the Master, take a full backup, and then sync the slaves from this copy.

090710 19:01:25 [ERROR] /opt/mysql/bin/mysqld: Disk is full writing '/mysqllog/binlog/hostname-3306-bin.000020'
 (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
090710 19:01:46 [ERROR] Error writing file '/mysqllog/slow_log/hostname_3306_slow_queries.log' (errno: 1)
090710 19:02:25 [ERROR] Error writing file '/mysqllog/binlog/hostname-3306-bin' (errno: 28)
090710 19:02:25 [ERROR] Could not use /mysqllog/binlog/hostname-3306-bin for logging (error 28).
  Turning logging off for the whole duration of the MySQL server process. 
  To turn it on again: fix the cause, shutdown the MySQL server and restart it.