Hello. I have the following problem. I was importing a large database to mysql using mysqldump. Unfortunately this filled up the whole disk, and mysqldump exited with an error that the table it is currently writing to is full. Checking df -h it shows that the disk usage is at 100%. I decided to drop the database I was importing, but rechecking df -h shows that it is still at 100%. I then looked for the cause of this and found a very large file under /var/lib/mysql. I think it is ibdata1. I deleted it and rechecked df -h, but it is stll at 100%. I then stopped mysql and finally the output of df -h was correct. However, when I try to restart mysql it outputs the following errors in the error log; it is in the attached file.
Thanks for anyone that could help.
InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 111129 12:51:23 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... InnoDB: Page directory corruption: infimum not pointed to 111129 12:51:23 InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex (LOTS OF ZEROES...) ;InnoDB: End of page dump 111129 12:56:28 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432 InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0 InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0 InnoDB: Page number (if stored to page already) 0, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a freshly allocated page 111129 12:56:28InnoDB: Error: trying to access a stray pointer 0x33987ff8 InnoDB: buf pool start is at 0xb3978000, end at 0xb4178000 InnoDB: Probable reason is database corruption or memory InnoDB: corruption. If this happens in an InnoDB database recovery, see InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: how to force recovery. 111129 12:56:28 InnoDB: Assertion failure in thread 3067451088 in file ../../../storage/innobase/include/buf0buf.ic line 264 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/forcing-recovery.html InnoDB: about forcing recovery. 111129 12:56:28 - 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 = 345919 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 /usr/sbin/mysqld(my_print_stacktrace+0x2d) [0xb763ecbd] /usr/sbin/mysqld(handle_segfault+0x494) [0xb730a854] [0xb7085400] /lib/tls/i686/nosegneg/libc.so.6(abort+0x182) [0xb6d88d42] /usr/sbin/mysqld(page_cur_search_with_match+0x9e3) [0xb755cdb3] /usr/sbin/mysqld(btr_cur_search_to_nth_level+0x5ae) [0xb74f2c8e] /usr/sbin/mysqld(btr_pcur_open_on_user_rec+0x73) [0xb75be6c3] /usr/sbin/mysqld(+0x46fc55) [0xb7512c55] /usr/sbin/mysqld(dict_load_sys_table+0x75) [0xb75195c5] /usr/sbin/mysqld(dict_boot+0xd27) [0xb75bf927] /usr/sbin/mysqld(innobase_start_or_create_for_mysql+0x1299) [0xb7595459] /usr/sbin/mysqld(+0x43e7e6) [0xb74e17e6] /usr/sbin/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x3f) [0xb741611f] /usr/sbin/mysqld(+0x411f2a) [0xb74b4f2a] /usr/sbin/mysqld(plugin_init(int*, char**, int)+0x8a7) [0xb74b8827] /usr/sbin/mysqld(+0x2698d2) [0xb730c8d2] /usr/sbin/mysqld(main+0x1fa) [0xb730ff9a] /lib/tls/i686/nosegneg/libc.so.6(__libc_start_main+0xe6) [0xb6d71bd6] /usr/sbin/mysqld(+0x182d81) [0xb7225d81] 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.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
