inodb文件损坏引起的err文件充满硬盘的问题

由于innodb文件损坏，这时虽然mysql能够启动，mysql会每隔几分钟尝试修复innodb文件，修复失败就会写错误到文件中，而且写得非常快，我们服务器不到12小时，就产生了220GB的错误日志，把硬盘写满了。

因此这种危害比mysql没有启动更严重

120711 13:52:11InnoDB: Assertion failure in thread 1 in file fil0fil.c line 3959
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Error: trying to access page number 1667323833 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.