Description:
Hi all,
my motherboard crashed, and an ssd disk also. I've moved the mysql data folder to an new ssd disk. The only, maybe, special thing is "innodb_file_per_table = 1", the rest of the my.cnf is standard.
When mysql starts now i get the following error:
--------------------------------------------------
100107 17:01:37 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 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 100107 17:01:38 - mysqld got signal 11 ;
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 = 346497 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) [0x7f919631f819]
mysqld(handle_segfault+0x36a) [0x7f919603744a]
/lib/libpthread.so.0 [0x7f91958a4a80]
mysqld(page_cur_insert_rec_low+0x59c) [0x7f91962521dc]
mysqld(page_cur_parse_insert_rec+0x577) [0x7f9196252cc7]
mysqld [0x7f919623d078]
mysqld(recv_recover_page+0x3fe) [0x7f919623ef5e]
mysqld(buf_page_io_complete+0x5a0) [0x7f91961f8fa0]
mysqld(fil_aio_wait+0x125) [0x7f9196212ba5]
mysqld [0x7f9196283690]
/lib/libpthread.so.0 [0x7f919589cfc7]
/lib/libc.so.6(clone+0x6d) [0x7f91943f85ad]
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.
----------------------------------------------------------
I've changed key_buffer_size, read_buffer_size, sort_buffer_size and max_threads in hundreds of values, the error has not gone.
i have also changed all ulimit parameters * 10.
-------------------------------------
ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 737280
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 10240
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 8192000
real-time priority (-r) 0
stack size (kbytes, -s) 81920
cpu time (seconds, -t) unlimited
max user processes (-u) 73728
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
-------------------------------------------------
I've updated to the current mysql version. Can someone give me an hint how i can get rid of this problem?
greetings,
Max
How to repeat:
I don't know... crash an mysql server and recover innodb data?
