解决mysql启动报错Starting MySQL.Manager of pid-file quit without updating file

解决mysql启动报错Starting MySQL.Manager of pid-file quit without updating file
错误日志:
120924 15:53:34 mysqld_safe Starting mysqld daemon with databases from /data0/mysql/3306/data
120924 15:53:34 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120924 15:53:34  InnoDB: Initializing buffer pool, size = 8.0M
120924 15:53:34  InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120924 15:53:34  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Page directory corruption: infimum not pointed to
120924 15:53:34  InnoDB: Page dump in ascii and hex (16384 bytes):

注意这句:
InnoDB: The log sequence number in ibdata files does not match
InnoDB的：在ibdata文件的日志序列号不匹配

可能ibdata文件损坏了
解决办法如下:
在my.cny 的[mysqld]中加入

# Size of each log file in a log group. You should set the combined size# of log files to about 25%-100% of your buffer pool size to avoid# unneeded buffer pool flush activity on log file overwrite. However,# note that a larger logfile size will increase the time needed for the# recovery process.innodb_log_file_size=10M# Number of threads allowed inside the InnoDB kernel. The optimal value# depends highly on the application, hardware as well as the OS# scheduler properties. A too high value may lead to thread thrashing.innodb_thread_concurrency=8innodb_force_recovery = 4max_allowed_packet=16M