mysql innodb 修複_關于mysql的innodb無法啟動修複的問題

我啟用了innodb_force_recovery = 1對mysql資料庫進行損壞修複.但是mysql很不給面子,CPU一直在吃,但是就是不給我啟動...導緻我無法導出,并回複資料,請問目前如何是好呢

下面是錯誤的log

140718 22:22:34 [Note] Plugin 'FEDERATED' is disabled.

140718 22:22:34 InnoDB: The InnoDB memory heap is disabled

140718 22:22:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins

140718 22:22:34 InnoDB: Compressed tables use zlib 1.2.7

140718 22:22:34 InnoDB: Using Linux native AIO

140718 22:22:34 InnoDB: Initializing buffer pool, size = 128.0M

140718 22:22:34 InnoDB: Completed initialization of buffer pool

140718 22:22:34 InnoDB: highest supported file format is Barracuda.

InnoDB: The log sequence number in ibdata files does not match

InnoDB: the log sequence number in the ib_logfiles!

140718 22:22: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...

140718 22:22:35 InnoDB: Error: space id and page n:o stored in the page

InnoDB: read in are 4294967295:4294967295, should be 0:451!

140718 22:22:35 InnoDB: Error: page 4294967295 log sequence number 18446744073709551615

InnoDB: is in the future! Current system log sequence number 12396895836.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

InnoDB: for more information.

InnoDB: Database page corruption on disk or a failed

InnoDB: file read of page 451.

InnoDB: You may have to recover from a backup.

140718 22:22:35 InnoDB: Page dump in ascii and hex (16384 bytes):

len 16384; hex fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff; 這裡有一堆f.由于限制字型發不出asc ;

InnoDB: End of page dump

14:09:03 UTC - mysqld got signal 6 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed,

something is definitely wrong and this may fail.

key_buffer_size=16777216

read_buffer_size=131072

max_used_connections=0

max_threads=151

thread_count=0

connection_count=0

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346079 K bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

stack_bottom = 0 thread_stack 0x30000

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

information that should help you find out what is causing the crash.