InnoDB: Unable to lock ./xxxxxx/xxxxx.ibd, error: 11 hatası.
InnoDB bir veritabanında sunucuyu resetledikten sonra aşağıdaki hatayı aldık.
120209 05:12:29 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data/ 120209 5:12:29 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 120209 5:12:29 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: Unable to lock ./xxxxxx/xxxxx.ibd, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 120209 5:12:29 InnoDB: Assertion failure in thread 47546054463296 in file fil/fil0fil.c line 635 InnoDB: Failing assertion: ret 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.1/en/forcing-recovery.html InnoDB: about forcing recovery. 120209 5:12:29 - 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=104857600 read_buffer_size=52428800 max_used_connections=0 max_threads=512 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 52536408 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 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 0x40000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x8ad46e] /usr/local/mysql/bin/mysqld(handle_segfault+0x322)[0x5e05c2] /lib64/libpthread.so.0[0x39a0a0e4c0] /lib64/libc.so.6(gsignal+0x35)[0x39a0230215] /lib64/libc.so.6(abort+0x110)[0x39a0231cc0] /usr/local/mysql/bin/mysqld[0x7acc5c] /usr/local/mysql/bin/mysqld[0x7acdf9] /usr/local/mysql/bin/mysqld(fil_space_get_size+0xde)[0x7b407e] /usr/local/mysql/bin/mysqld(fil_check_adress_in_tablespace+0x9)[0x7b4159] /usr/local/mysql/bin/mysqld(trx_sys_doublewrite_init_or_restore_pages+0x2d5)[0x82b6d5] /usr/local/mysql/bin/mysqld(recv_recovery_from_checkpoint_start+0x175b)[0x7dbe0b] /usr/local/mysql/bin/mysqld(innobase_start_or_create_for_mysql+0x115f)[0x81b8cf] /usr/local/mysql/bin/mysqld[0x777d64] /usr/local/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x31)[0x6cf411] /usr/local/mysql/bin/mysqld[0x75513a] /usr/local/mysql/bin/mysqld(_Z11plugin_initPiPPci+0x875)[0x757c95] /usr/local/mysql/bin/mysqld[0x5e0d95] /usr/local/mysql/bin/mysqld(main+0x1c1)[0x5e50b1] /lib64/libc.so.6(__libc_start_main+0xf4)[0x39a021d974] /usr/local/mysql/bin/mysqld(fmod+0x62)[0x513c0a] 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. 120209 05:12:29 mysqld_safe mysqld from pid file /usr/local/mysql/data//xxxxxx.pid ended
Çözüm olarak mysql i durdurup *.ibd dosyalarını taşıyıp tekrar cp -a ile kopyaladık ve mysql i çalıştırdık sorunumuz düzeldi.
Basit shell script şöyle :
#!/bin/bash for i in `ls -a *.ibd` do mv $i $i.bak cp -a $i.bak $i done
Posted in Linux, MySQL on February 9th, 2012 by Kürşad DARA | | 0 Comments
