之前我已经修复了mysql并且它一直在崩溃。我做的是我停止了mysql服务器,并删除了ib_logfile1和ib_logfile0。并编辑了我的etc / mysql / my.cnf并将大小调整为32m到64m这就是my.cnf的样子
# INNODB #
innodb_flush_method = O_DIRECT
innodb_log_files_in_group = 2
innodb_log_file_size = 64M
innodb_flush_log_at_trx_commit = 1
innodb_file_per_table = 1
innodb_buffer_pool_size = 8M
过了一会儿,它再次坠毁。有这个错误
140304 22:25:05 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140304 22:25:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140304 22:25:34 [Note] Plugin 'FEDERATED' is disabled.
140304 22:25:34 InnoDB: Initializing buffer pool, size = 8.0M
140304 22:25:34 InnoDB: Completed initialization of buffer pool
140304 22:25:34 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 64 MB
InnoDB: Database physically writes the file full: wait...
140304 22:25:34 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 64 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140304 22:25:35 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...
140304 22:25:35 InnoDB: Started; log sequence number 0 44556
140304 22:25:35 [Warning] 'user' entry 'root@sqldb' ignored in --skip-name-resolve mode.
140304 22:25:35 [Note] Event Scheduler: Loaded 0 events
140304 22:25:35 [Note] /usr/sbin/mysqld: ready for connections.
关于如何解决此问题的任何建议?