help-innodb corupt


Status
Not open for further replies.
M

megdi

Apprentice 1.0
Halo fren
saya mau tanya nih, salah satu seever ada yang innodb corupt. Sebelumnya gak bisa start mysql nya setelah ganti default ke myisam bisa start lagi.
Tapi pas jalananin repair ternyata corupt.

Masalahnya backupnya kemarin saya hapus, dan belum sempet backup ulang error :(

Bisa diperbaiki gak ya?
berikut status ketika running repair database
Code: 
Error    : Unknown storage engine 'InnoDB'
error    : Corrupt
waktu cek log hostname.err, berikut detail last log nya

Code: 
InnoDB: is in the future! Current system log sequence number 2163128138.
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.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-07-18 03:29:35 7f9a5db87820 InnoDB: Error: page 300 log sequence number 2163226887
InnoDB: is in the future! Current system log sequence number 2163128138.
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.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: 4 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 25477376
2017-07-18  3:29:35 140300974061600 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
InnoDB: Apply batch completed
InnoDB: Cleaning up trx with id 25477227
2017-07-18 03:29:35 7f9a5db87820  InnoDB: Assertion failure in thread 140300974061600 in file trx0trx.cc line 467
InnoDB: Failing assertion: trx->update_undo == NULL
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
170718  3:29:35 [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 https://mariadb.com/kb/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: 10.1.21-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 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 = 0x0 thread_stack 0x48400
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f9a5e611a9b]
/usr/sbin/mysqld(handle_fatal_signal+0x4d5)[0x7f9a5e16d8f5]
/lib64/libpthread.so.0(+0xf7e0)[0x7f9a5d7707e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f9a5bb965e5]
/lib64/libc.so.6(abort+0x175)[0x7f9a5bb97dc5]
/usr/sbin/mysqld(+0x831462)[0x7f9a5e3d1462]
/usr/sbin/mysqld(+0x826b1d)[0x7f9a5e3c6b1d]
/usr/sbin/mysqld(+0x784679)[0x7f9a5e324679]
/usr/sbin/mysqld(+0x811a2e)[0x7f9a5e3b1a2e]
/usr/sbin/mysqld(+0x7321e5)[0x7f9a5e2d21e5]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x68)[0x7f9a5e16fda8]
/usr/sbin/mysqld(+0x46d4f5)[0x7f9a5e00d4f5]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x8da)[0x7f9a5e00e45a]
mysys/stacktrace.c:268(my_print_stacktrace)[0x7f9a5df6da75]
log/log0recv.cc:3585(recv_recovery_from_checkpoint_finish())[0x7f9a5df703e2]
handler/ha_innodb.cc:4446(innobase_init)[0x7f9a5bb82d1d]
sql/handler.cc:513(ha_initialize_handlerton(st_plugin_int*))[0x7f9a5df643f9]
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.
170718 03:29:36 mysqld_safe mysqld from pid file /var/lib/mysql/offcc.pid ended
170718 04:20:48 mysqld_safe A mysqld process already exists
170718 04:40:55 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2017-07-18  4:40:55 139737003612192 [Note] /usr/sbin/mysqld (mysqld 10.1.21-MariaDB) starting as process 13570 ...
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: The InnoDB memory heap is disabled
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Using Linux native AIO
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Using generic crc32 instructions
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Completed initialization of buffer pool
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Highest supported file format is Barracuda.
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2163112690
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Database was not shutdown normally!
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Starting crash recovery.
2017-07-18  4:40:55 139737003612192 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-07-18  4:40:57 139737003612192 [Note] InnoDB: Restoring possible half-written data pages
2017-07-18  4:40:57 139737003612192 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Set innodb_force_recovery to ignore this error.
2017-07-18  4:40:57 139737003612192 [ERROR] Plugin 'InnoDB' init function returned error.
2017-07-18  4:40:57 139737003612192 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-07-18  4:40:57 139737003612192 [Note] Plugin 'FEEDBACK' is disabled.
2017-07-18  4:40:57 139737003612192 [Note] Server socket created on IP: '::'.
2017-07-18  4:40:57 139736309775104 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1286: Unknown storage engine 'InnoDB'
2017-07-18  4:40:57 139737003612192 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.21-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
 
mustafaramadhan

mustafaramadhan

Hosting Guru
junior riau said:
momok para hoster :D
Click to expand...
Maka saya lebih nyaman pakai myisam/aria sebagai storage-engine untuk mysql. Jika ada yang corrupt, cukup jalan 'sh /script/mysql-optimize --select=repair' (tentunya jika pakai Kloxo-MR).
 
Status
Not open for further replies.

Top