Форум пользователей MySQL

Были удаленны на горячую файлы ib_logfile0 и ib_logfile1.

сейчас при старте mysqld получаем(см. ниже), видно, что пытается синхронизировать, но....

может кто поможет, как вернуть рабочее состояние базы СУБД

121103 0:26:20 [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!
121103 0:26:20 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...
121103 0:26:20 InnoDB: Error: page 7 log sequence number 9 1303691825
InnoDB: is in the future! Current system log sequence number 8 3724248076.
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.1/en/ … overy.html
InnoDB: for more information.
...........................................................................
121103 0:26:20 InnoDB: Assertion failure in thread 140455538763520 in file ../../../storage/innobase/btr/btr0cur.c line 163
InnoDB: Failing assertion: btr_page_get_next(get_page, mtr) == buf_frame_get_page_no(page)
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/ … overy.html
InnoDB: about forcing recovery.
121103 0:26:20 - 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
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346514 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 0x30000
mysqld(my_print_stacktrace+0x29) [0x7fbe61d19829]
mysqld(handle_segfault+0x404) [0x7fbe61a23b14]
/lib/libpthread.so.0(+0xef60) [0x7fbe61285f60]
/lib/libc.so.6(gsignal+0x35) [0x7fbe5fd29165]
/lib/libc.so.6(abort+0x180) [0x7fbe5fd2bf70]
mysqld(+0x532862) [0x7fbe61be5862]
mysqld(btr_cur_search_to_nth_level+0x9ef) [0x7fbe61be9a6f]
mysqld(btr_pcur_restore_position+0x2ab) [0x7fbe61ca697b]
mysqld(+0x5feb57) [0x7fbe61cb1b57]
mysqld(row_undo_ins+0x177) [0x7fbe61cb2127]
mysqld(row_undo_step+0x256) [0x7fbe61c73726]
mysqld(que_run_threads+0x4fe) [0x7fbe61c56e5e]
mysqld(trx_rollback_or_clean_all_without_sess+0x367) [0x7fbe61c8f287]
/lib/libpthread.so.0(+0x68ba) [0x7fbe6127d8ba]
/lib/libc.so.6(clone+0x6d) [0x7fbe5fdc602d]
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.