Description:
i found error below
please let me know how to solve it
100508 7:32:55 InnoDB: Error: Write to file /mysql_data/ibdata1 failed at offset 1 37109760.
InnoDB: 16384 bytes should have been written, only -1 were written.
InnoDB: Operating system error number 5.
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 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
100508 7:32:55InnoDB: Assertion failure in thread 1833733040 in file os0file.c line 4012
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.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Thread 1761979312 stopped in file btr0pcur.c line 236
100508 7:32:55 - mysqld got signal 11;
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=4194304
read_buffer_size=4190208
max_used_connections=221
max_connections=220
threads_connected=220
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2706574 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
Attempting backtrace. You can use the following information to find out
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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...
Cannot determine thread, fp=0x6d4c7f0c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81c2007
0x83e5130
0x83b57e6
0x82fc7eb
0x8c1371
0x74affe
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
Number of processes running now: 0
100508 07:33:20 mysqld restarted
100508 7:33:20 [Warning] Can't create test file /mysql_data/db-opsrv1.lower-test
100508 7:33:20 [Warning] Can't create test file /mysql_data/db-opsrv1.lower-test
100508 7:33:20 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...
100508 7:33:40 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 73 2901710816.
InnoDB: Doing recovery: scanned up to log sequence number 73 2902643793
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 0 2136807680
100508 7:33:43 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 1864183, file name /mysql_log/mysql-bin.000680
InnoDB: Starting in background the rollback of uncommitted transactions
100508 7:35:45 InnoDB: Rolling back trx with id 0 2136807011, 1 rows to undo
100508 7:35:45 InnoDB: Started; log sequence number 73 2902643793
100508 7:35:45 [Note] Recovering after a crash using /mysql_log/mysql-bin
InnoDB: Rolling back of trx id 0 2136807011 completed
100508 7:35:45 InnoDB: Rollback of non-prepared transactions completed
How to repeat:
-
