Merhaba,
MySQL crash olmasi neticesinde innodb verilerim bozuldu ve 2 gundur recover edemedim. Loglar asagida ancak loglar icerisinde bulabildigim anahtar kelimeler ile mysqlin sitesi dahil 100lerce sayfayi arastirdigimi belirtmek istiyorum. Yinede bildiginiz tum yontemleri yazmanizi istirham ediyorum. Aug 10 13:32:48 myhost mysqld[4396]: 100810 13:32:48 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432 Aug 10 13:32:48 myhost mysqld[4396]: InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0 Aug 10 13:32:48 myhost mysqld[4396]: InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0 Aug 10 13:32:48 myhost mysqld[4396]: InnoDB: Page number (if stored to page already) 0, Aug 10 13:32:48 myhost mysqld[4396]: InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 Aug 10 13:32:48 myhost mysqld[4396]: InnoDB: Page directory corruption: supremum not pointed to Aug 10 13:32:48 myhost mysqld[4396]: 100810 13:32:48 InnoDB: Page dump in ascii and hex (16384 bytes): Aug 10 13:32:48 myhost mysqld[4396]: len 16384; hex 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000 Aug 10 13:32:49 myhost mysqld[4396]: 100810 13:32:49 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432 Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0 Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0 Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: Page number (if stored to page already) 0, Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 Aug 10 13:32:49 myhost mysqld[4396]: 100810 13:32:49InnoDB: Error: trying to access a stray pointer 0x24033ff8 Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: buf pool start is at 0xa4024000, end at 0xb4024000 Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: Probable reason is database corruption or memory Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: corruption. If this happens in an InnoDB database recovery, see Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: how to force recovery. Aug 10 13:32:49 myhost mysqld[4396]: 100810 13:32:49InnoDB: Assertion failure in thread 3083470528 in file ./../include/buf0buf.ic line 268 Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: We intentionally generate a memory trap. Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com. Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: If you get repeated assertion failures or crashes, even Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: immediately after the mysqld startup, there may be Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: corruption in the InnoDB tablespace. Please refer to Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html Aug 10 13:32:49 myhost mysqld[4396]: InnoDB: about forcing recovery. Aug 10 13:32:49 myhost mysqld[4396]: 100810 13:32:49 - mysqld got signal 11; Aug 10 13:32:49 myhost mysqld[4396]: This could be because you hit a bug. It is also possible that this binary Aug 10 13:32:49 myhost mysqld[4396]: or one of the libraries it was linked against is corrupt, improperly built, Aug 10 13:32:49 myhost mysqld[4396]: or misconfigured. This error can also be caused by malfunctioning hardware. Aug 10 13:32:49 myhost mysqld[4396]: We will try our best to scrape up some info that will hopefully help diagnose Aug 10 13:32:49 myhost mysqld[4396]: the problem, but since we have already crashed, something is definitely wrong Aug 10 13:32:49 myhost mysqld[4396]: and this may fail. Aug 10 13:32:49 myhost mysqld[4396]: Aug 10 13:32:49 myhost mysqld[4396]: key_buffer_size=0 Aug 10 13:32:49 myhost mysqld[4396]: read_buffer_size=131072 Aug 10 13:32:49 myhost mysqld[4396]: max_used_connections=0 Aug 10 13:32:49 myhost mysqld[4396]: max_connections=150 Aug 10 13:32:49 myhost mysqld[4396]: threads_connected=0 Aug 10 13:32:49 myhost mysqld[4396]: It is possible that mysqld could use up to Aug 10 13:32:49 myhost mysqld[4396]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 326398 K Aug 10 13:32:49 myhost mysqld[4396]: bytes of memory Aug 10 13:32:49 myhost mysqld[4396]: Hope that's ok; if not, decrease some variables in the equation. Aug 10 13:32:49 myhost mysqld[4396]: Aug 10 13:32:49 myhost mysqld[4396]: thd=(nil) Aug 10 13:32:49 myhost mysqld[4396]: Attempting backtrace. You can use the following information to find out Aug 10 13:32:49 myhost mysqld[4396]: where mysqld died. If you see no messages after this, something went Aug 10 13:32:49 myhost mysqld[4396]: terribly wrong... Aug 10 13:32:49 myhost mysqld[4396]: Cannot determine thread, fp=0xbfa53148, backtrace may not be correct. Aug 10 13:32:49 myhost mysqld[4396]: Stack range sanity check OK, backtrace follows: Aug 10 13:32:49 myhost mysqld[4396]: 0x81f2333 Aug 10 13:32:49 myhost mysqld[4396]: 0x8429628 Aug 10 13:32:49 myhost mysqld[4396]: 0x83a08c4 Aug 10 13:32:49 myhost mysqld[4396]: 0x83aa936 Aug 10 13:32:49 myhost mysqld[4396]: 0x834ca2d Aug 10 13:32:49 myhost mysqld[4396]: 0x834e4c2 Aug 10 13:32:49 myhost mysqld[4396]: 0x833dda4 Aug 10 13:32:49 myhost mysqld[4396]: 0x833b47a Aug 10 13:32:49 myhost mysqld[4396]: 0x82b6f70 Aug 10 13:32:49 myhost mysqld[4396]: 0x82abad2 Aug 10 13:32:49 myhost mysqld[4396]: 0x81f129b Aug 10 13:32:49 myhost mysqld[4396]: 0x81f356a Aug 10 13:32:49 myhost mysqld[4396]: 0xb7cb8450 Aug 10 13:32:49 myhost mysqld[4396]: 0x8164871 Aug 10 13:32:49 myhost mysqld[4396]: New value of fp=(nil) failed sanity check, terminating stack trace! Aug 10 13:32:49 myhost mysqld[4396]: Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved Aug 10 13:32:49 myhost mysqld[4396]: stack trace is much more helpful in diagnosing the problem, so please do Aug 10 13:32:49 myhost mysqld[4396]: resolve it Aug 10 13:32:49 myhost mysqld[4396]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains Aug 10 13:32:49 myhost mysqld[4396]: information that should help you find out what is causing the crash. -- /** * @AUTHOR Atıf CEYLAN * Software Developer & System Admin * http://www.atifceylan.com */
_______________________________________________ Linux-sunucu E-Posta Listesi [email protected] Liste kurallarını http://liste.linux.org.tr/kurallar.php bağlantısından okuyabilirsiniz; Bu Listede neden bulunduğunuzu bilmiyorsanız veya artık bu listeden gelen e-postaları almak istemiyorsanız aşağıdaki bağlantı adresini kullanarak 1 dakika içinde üyeliğinizi sonlandırabilirsiniz. https://liste.linux.org.tr/mailman/listinfo/linux-sunucu
