Description:
110416 15:36:22 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...
110416 15:36:22 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 114 1885003064.
InnoDB: Doing recovery: scanned up to log sequence number 114 1885801267
InnoDB: Transaction 0 1008846061 was in the XA prepared state.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 0 1008846336
110416 15:36:22 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 56122263, file name ./posmysql-bin.001203
InnoDB: Starting in background the rollback of uncommitted transactions
110416 15:36:24 InnoDB: Rollback of non-prepared transactions completed
110416 15:36:24 InnoDB: Started; log sequence number 114 1885801267
110416 15:36:24 [Note] Recovering after a crash using posmysql-bin
110416 15:36:25 [Note] Starting crash recovery...
110416 15:36:25 InnoDB: Starting recovery for XA transactions...
110416 15:36:25 InnoDB: Transaction 0 1008846061 in prepared state after recovery
110416 15:36:25 InnoDB: Transaction contains changes to 1264 rows
110416 15:36:25 InnoDB: 1 transactions in prepared state after recovery
110416 15:36:25 [Note] Found 1 prepared transaction(s) in InnoDB
110416 15:36:25InnoDB: Assertion failure in thread 1075591488 in file fsp0fsp.c line 1569
InnoDB: Failing assertion: frag_n_used > 0
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.
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=0
read_buffer_size=131072
max_used_connections=0
max_connections=300
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 652797 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
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xbfffe25c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x818bbf0
0x83464fb
0x8346617
0x8347548
0x8321a57
0x831ee6f
0x831fc75
0x824b052
0x823d4cb
0x8206617
0x8209792
0x818e3b8
0x400be210
0x8102ca1
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.
110416 16:00:34 InnoDB: Database was not shut down normally!
How to repeat:
Everytime we restore the data ,after 4-5 days database gets crashed and show above message in log file.
