090908 15:22:07 InnoDB: Error: Write to file ./ibdata1 failed at offset 0 134217728. InnoDB: 393216 bytes should have been written, only 139264 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html 090908 15:22:07 InnoDB: Assertion failure in thread 1107310912 in file os/os0file.c line 4142 InnoDB: Failing assertion: ret 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. /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x89b4be] /usr/local/mysql/bin/mysqld(handle_segfault+0x322)[0x5d29f2] /lib64/libpthread.so.0[0x2b5378b3cc00] /lib64/libc.so.6(gsignal+0x35)[0x2b5379120bb5] /lib64/libc.so.6(abort+0x110)[0x2b5379121fb0] /usr/local/mysql/bin/mysqld(os_aio_simulated_handle+0x933)[0x7cf683] /usr/local/mysql/bin/mysqld(fil_aio_wait+0x3f)[0x7986af] /usr/local/mysql/bin/mysqld[0x804c70] /lib64/libpthread.so.0[0x2b5378b35143] /lib64/libc.so.6(__clone+0x6d)[0x2b53791b18cd] 090908 15:22:07 - 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=402653184 read_buffer_size=1048576 max_used_connections=240 max_threads=500 threads_connected=68 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1422298 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 0x40000 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. 090908 15:22:07 mysqld_safe Number of processes running now: 0 090908 15:22:07 mysqld_safe mysqld restarted InnoDB: Log scan progressed past the checkpoint lsn 285 2183965446 090908 15:22:08 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: Warning: database page corruption or a failed InnoDB: file read of page 8200. InnoDB: Trying to recover it from the doublewrite buffer. InnoDB: Recovered the page from the doublewrite buffer. InnoDB: Doing recovery: scanned up to log sequence number 285 2189208064 InnoDB: Doing recovery: scanned up to log sequence number 285 2194450944 InnoDB: Doing recovery: scanned up to log sequence number 285 2199693824 InnoDB: Doing recovery: scanned up to log sequence number 285 2204936704 InnoDB: Doing recovery: scanned up to log sequence number 285 2210179584 InnoDB: Doing recovery: scanned up to log sequence number 285 2215422464 InnoDB: Doing recovery: scanned up to log sequence number 285 2220665344 InnoDB: Doing recovery: scanned up to log sequence number 285 2225908224 InnoDB: Doing recovery: scanned up to log sequence number 285 2231151104 InnoDB: Doing recovery: scanned up to log sequence number 285 2236393984 InnoDB: Doing recovery: scanned up to log sequence number 285 2241636864 InnoDB: Doing recovery: scanned up to log sequence number 285 2246879744 InnoDB: Doing recovery: scanned up to log sequence number 285 2252122624 InnoDB: Doing recovery: scanned up to log sequence number 285 2257365504 InnoDB: Doing recovery: scanned up to log sequence number 285 2262608384 InnoDB: Doing recovery: scanned up to log sequence number 285 2267851264 InnoDB: Doing recovery: scanned up to log sequence number 285 2273094144 InnoDB: Doing recovery: scanned up to log sequence number 285 2278337024 InnoDB: Doing recovery: scanned up to log sequence number 285 2283579904 InnoDB: Doing recovery: scanned up to log sequence number 285 2288822784 InnoDB: Doing recovery: scanned up to log sequence number 285 2294065664 InnoDB: Doing recovery: scanned up to log sequence number 285 2299308544 InnoDB: Doing recovery: scanned up to log sequence number 285 2304551424 InnoDB: Doing recovery: scanned up to log sequence number 285 2309794304 InnoDB: Doing recovery: scanned up to log sequence number 285 2315037184 InnoDB: Doing recovery: scanned up to log sequence number 285 2320280064 InnoDB: Doing recovery: scanned up to log sequence number 285 2325522944 InnoDB: Doing recovery: scanned up to log sequence number 285 2330765824 InnoDB: Doing recovery: scanned up to log sequence number 285 2336008704 InnoDB: Doing recovery: scanned up to log sequence number 285 2341251584 InnoDB: Doing recovery: scanned up to log sequence number 285 2346494464 InnoDB: Doing recovery: scanned up to log sequence number 285 2351737344 InnoDB: Doing recovery: scanned up to log sequence number 285 2356980224 InnoDB: Doing recovery: scanned up to log sequence number 285 2362223104 InnoDB: Doing recovery: scanned up to log sequence number 285 2367465984 InnoDB: Doing recovery: scanned up to log sequence number 285 2372708864 InnoDB: Doing recovery: scanned up to log sequence number 285 2377951744 InnoDB: Doing recovery: scanned up to log sequence number 285 2383194624 InnoDB: Doing recovery: scanned up to log sequence number 285 2388437504 InnoDB: Doing recovery: scanned up to log sequence number 285 2393680384 InnoDB: Doing recovery: scanned up to log sequence number 285 2398923264 InnoDB: Doing recovery: scanned up to log sequence number 285 2404166144 InnoDB: Doing recovery: scanned up to log sequence number 285 2409409024 InnoDB: Doing recovery: scanned up to log sequence number 285 2414651904 InnoDB: Doing recovery: scanned up to log sequence number 285 2419894784 InnoDB: Doing recovery: scanned up to log sequence number 285 2424714974 InnoDB: 5 transaction(s) which must be rolled back or cleaned up InnoDB: in total 78 row operations to undo InnoDB: Trx id counter is 0 504567552 090908 15:22:48 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 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 18056107, file name ./master-bin.000138 InnoDB: Starting in background the rollback of uncommitted transactions 090908 15:24:17 InnoDB: Rolling back trx with id 0 504567080, 1 rows to undo 090908 15:24:17 InnoDB: Started; log sequence number 285 2424714974 InnoDB: Rolling back of trx id 0 504567080 completed 090908 15:24:17 InnoDB: Rolling back trx with id 0 504567079, 2 rows to undo InnoDB: Rolling back of trx id 0 504567079 completed 090908 15:24:17 InnoDB: Rolling back trx with id 0 504567075, 2 rows to undo InnoDB: Rolling back of trx id 0 504567075 completed 090908 15:24:17 InnoDB: Rolling back trx with id 0 504567072, 71 rows to undo 090908 15:24:17 [Note] Recovering after a crash using master-bin InnoDB: Rolling back of trx id 0 504567072 completed 090908 15:24:17 InnoDB: Rolling back trx with id 0 504567069, 2 rows to undo InnoDB: Rolling back of trx id 0 504567069 completed 090908 15:24:17 InnoDB: Rollback of non-prepared transactions completed 090908 15:24:17 [Note] Starting crash recovery... 090908 15:24:17 [Note] Crash recovery finished. 090908 15:24:17 [Note] Event Scheduler: Loaded 0 events 090908 15:24:17 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.1.31-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)