List:General Discussion« Previous MessageNext Message »
From:Peter Date:June 21 2013 8:04am
Subject:Re: help: innodb database cannot recover
View as plain text  

>boah you *must not* remove ibdata1
>it contains the global tablespace even with file_per_table

>"ib_logfile0" and "ib_logfile1" may be removed, but make sure you have
>a as cinsistent as possible backup of the whole datadir

I removed "ib_logfile0" and "ib_logfile1" and restarted mysql with
innodb_force_recovery=1,
mysql keeps crashing and restart:
 

thd: 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 = (nil) thread_stack 0x30000
/usr/libexec/mysqld(my_print_stacktrace+0x2e) [0x84bbbae]
/usr/libexec/mysqld(handle_segfault+0x4bc) [0x81eca1c]
[0xf57fe400]
[0xf57fe416]
/lib/libc.so.6(gsignal+0x51) [0x45a7bb71]
/lib/libc.so.6(abort+0x17a) [0x45a7d44a]
/usr/libexec/mysqld(fil_io+0x377) [0x83ba177]
/usr/libexec/mysqld() [0x83a257b]
/usr/libexec/mysqld(buf_read_page+0x282) [0x83a3132]
/usr/libexec/mysqld(buf_page_get_gen+0x351) [0x839c111]
/usr/libexec/mysqld(btr_cur_search_to_nth_level+0x3c1) [0x838ca31]
/usr/libexec/mysqld(row_search_index_entry+0x79) [0x840d3c9]
/usr/libexec/mysqld() [0x840bf97]
/usr/libexec/mysqld(row_purge_step+0x574) [0x840d1e4]
/usr/libexec/mysqld(que_run_threads+0x535) [0x83fa815]
/usr/libexec/mysqld(trx_purge+0x365) [0x8427e25]
/usr/libexec/mysqld(srv_master_thread+0x75b) [0x842009b]
/lib/libpthread.so.0() [0x45bf09e9]
/lib/libc.so.6(clone+0x5e) [0x45b2dc2e]
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.
130620 00:47:21 mysqld_safe Number of processes running now: 0
130620 00:47:21 mysqld_safe mysqld restarted
InnoDB: Error: tablespace size stored in header is 456832 pages, but
InnoDB: the sum of data file sizes is only 262080 pages
InnoDB: Cannot start InnoDB. The tail of the system tablespace is
InnoDB: missing. Have you edited innodb_data_file_path in my.cnf in an
InnoDB: inappropriate way, removing ibdata files from there?
InnoDB: You can set innodb_force_recovery=1 in my.cnf to force
InnoDB: a startup if you are trying to recover a badly corrupt database.
130620  0:47:22 [ERROR] Plugin 'InnoDB' init function returned error.
130620  0:47:22 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.


if I set  innodb_force_recovery=4 to restart mysql and then run mysqldump, i got the
following error:
mysqldump: Got error: 2013: Lost connection to MySQL server during query when using LOCK
TABLES

it looks that all data from innodb is messed up and gone forever even though *.frm is
still there.

Peter
Thread
help: innodb database cannot recoverPeter20 Jun
  • Re: help: innodb database cannot recoverReindl Harald20 Jun
  • Re: help: innodb database cannot recoverManuel Arostegui20 Jun
    • Re: help: innodb database cannot recoverPeter20 Jun
      • Re: help: innodb database cannot recoverManuel Arostegui20 Jun
        • Re: help: innodb database cannot recoverPeter20 Jun
          • Re: help: innodb database cannot recoverPeter20 Jun
            • Re: help: innodb database cannot recoverReindl Harald20 Jun
              • Re: help: innodb database cannot recoverPeter21 Jun
                • Re: help: innodb database cannot recoverJohan De Meersman21 Jun
      • Re: help: innodb database cannot recoverReindl Harald20 Jun
        • Re: help: innodb database cannot recoverPeter20 Jun
          • Re: help: innodb database cannot recoverPeter20 Jun