数据库启动不了了，好像收ibdata1的问题

hzjixiang

数据库启动不了了，好像收ibdata1的问题，删掉这个问题就能启动，但是数据也没有了。 求大神帮忙

hzjixiang

151213 22:31:45 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var 151213 22:31:45 InnoDB: The InnoDB memory heap is disabled 151213 22:31:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins 151213 22:31:45 InnoDB: Compressed tables use zlib 1.2.3 151213 22:31:45 InnoDB: Initializing buffer pool, size = 16.0M 151213 22:31:45 InnoDB: Completed initialization of buffer pool 151213 22:31:45 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 79177740 151213 22:31:45 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: Doing recovery: scanned up to log sequence number 79178880 InnoDB: Transaction FF207 was in the XA prepared state. InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 0 row operations to undo InnoDB: Trx id counter is FFA00 151213 22:31:45 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 366, file name ./mysql-bin.000024 151213 22:31:45 InnoDB: Waiting for the background threads to start InnoDB: Starting in background the rollback of uncommitted transactions 151213 22:31:45 InnoDB: Rollback of non-prepared transactions completed 151213 22:31:46 InnoDB: 5.5.37 started; log sequence number 79178880 151213 22:31:46 InnoDB: Starting recovery for XA transactions... 151213 22:31:46 InnoDB: Transaction FF207 in prepared state after recovery 151213 22:31:46 InnoDB: Transaction contains changes to 0 rows 151213 22:31:46 InnoDB: 1 transactions in prepared state after recovery 151213 22:31:46 [Note] Found 1 prepared transaction(s) in InnoDB 151213 22:31:46 InnoDB: Assertion failure in thread 3070089024 in file fut0lst.ic line 83 InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. 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.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 14:31:46 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=262144 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 = 133467 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 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)[0x8391fc3] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x432)[0x8285862] [0xb7749500] /lib/libc.so.6(abort+0x17a)[0xb720314a] /usr/local/mysql/bin/mysqld[0x8448cf9] /usr/local/mysql/bin/mysqld[0x8448e76] /usr/local/mysql/bin/mysqld[0x83d72b8] /usr/local/mysql/bin/mysqld[0x83e9aa4] /usr/local/mysql/bin/mysqld[0x83e8373] /usr/local/mysql/bin/mysqld[0x83e878a] /usr/local/mysql/bin/mysqld[0x83decc9] /usr/local/mysql/bin/mysqld[0x848654e] /usr/local/mysql/bin/mysqld[0x848669c] /usr/local/mysql/bin/mysqld[0x83dfaa1] /usr/local/mysql/bin/mysqld[0x83dfead] /usr/local/mysql/bin/mysqld[0x839f980] /usr/local/mysql/bin/mysqld[0x839f9c7] /usr/local/mysql/bin/mysqld[0x828a963]

licess

可以在/etc/my.cnf 里[mysqld]
下面加上innodb_force_recovery=6

启动mysql后备份数据，尝试修复表，再去掉innodb_force_recovery=6 重启看看能否正常

hzjixiang

感谢军哥，已经完美解决了！