mysql - innodb 문제 innodb_force_recovery

crash ... errors..

                 t eD iI   N;
InnoDB: End of page dump
140915 12:19:26  InnoDB: Page checksum 1570298453 (32bit_calc: 3018546506), prior-to-4.0.14-form checksum 1152805193
InnoDB: stored checksum 1570298453, prior-to-4.0.14-form stored checksum 1152805193
InnoDB: Page lsn 69 2816875854, low 4 bytes of lsn at page end 2816875854
InnoDB: Page number (if stored to page already) 4,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
InnoDB: Page may be an index page where index id is 18446744069414584320
140915 12:19:26  InnoDB: Assertion failure in thread 139780984702912 in file page0cur.c line 905
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.
140915 12:19:26 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 5.5.39-MariaDB-1~saucy-log
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=0
max_threads=302
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1991930 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f214c7efdae]
/usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7f214c3e1f07]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfbb0)[0x7f214b491bb0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f214a4aef77]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f214a4b25e8]
/usr/sbin/mysqld(+0x816543)[0x7f214c730543]
/usr/sbin/mysqld(+0x7f9e4c)[0x7f214c713e4c]
/usr/sbin/mysqld(+0x7fbea6)[0x7f214c715ea6]
/usr/sbin/mysqld(+0x780253)[0x7f214c69a253]
/usr/sbin/mysqld(+0x791518)[0x7f214c6ab518]
/usr/sbin/mysqld(+0x77ab5b)[0x7f214c694b5b]
/usr/sbin/mysqld(+0x7dc453)[0x7f214c6f6453]
/usr/sbin/mysqld(+0x795b75)[0x7f214c6afb75]
/usr/sbin/mysqld(+0x72d009)[0x7f214c647009]
/usr/sbin/mysqld(+0x6e8b9e)[0x7f214c602b9e]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x7f214c3e4938]
/usr/sbin/mysqld(+0x38dbd5)[0x7f214c2a7bd5]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x531)[0x7f214c2acb51]
/usr/sbin/mysqld(+0x2f1282)[0x7f214c20b282]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x5ca)[0x7f214c2101ca]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f214a499de5]
/usr/sbin/mysqld(+0x2ec6f7)[0x7f214c2066f7]
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.
140915 12:19:26 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended