120221  3:53:51  InnoDB: Assertion failure in thread 1299265856 in file btr/btr0cur.c line 245
InnoDB: Failing assertion: page_is_comp(get_block->frame) == page_is_comp(page)
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.
120221  3:53:51 - 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=104857600
read_buffer_size=1048576
max_used_connections=14
max_threads=3200
threads_connected=9
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3732150 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 0x80000
/u01/mysql/libexec/mysqld(my_print_stacktrace+0x35)[0x884b95]
/u01/mysql/libexec/mysqld(handle_segfault+0x31d)[0x5bcfcd]
/lib64/libpthread.so.0[0x3453e0e7c0]
/lib64/libc.so.6(gsignal+0x35)[0x3453630265]
/lib64/libc.so.6(abort+0x110)[0x3453631d10]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab31f797e]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab31fa939]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab32abae8]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab32aa3c1]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab32ab37a]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab3294774]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab32c9307]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab32c0820]
/lib64/libpthread.so.0[0x3453e064a7]
/lib64/libc.so.6(clone+0x6d)[0x34536d3c2d]
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.
120221 03:53:55 mysqld_safe Number of processes running now: 0
120221 03:53:55 mysqld_safe mysqld restarted
120221  3:53:55 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120221  3:53:55 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120221  3:53:55 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
120221  3:53:58  InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 2027636753953
120221  3:53:59  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
120221  3:53:59  InnoDB: Warning: allocated tablespace 3954, old maximum was 0
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2027641996800
InnoDB: Doing recovery: scanned up to log sequence number 2027647239680
InnoDB: Doing recovery: scanned up to log sequence number 2027652482560
InnoDB: Doing recovery: scanned up to log sequence number 2027657725440
InnoDB: Doing recovery: scanned up to log sequence number 2027662968320
InnoDB: Doing recovery: scanned up to log sequence number 2027668211200
InnoDB: Doing recovery: scanned up to log sequence number 2027673454080
InnoDB: Doing recovery: scanned up to log sequence number 2027678696960
InnoDB: Doing recovery: scanned up to log sequence number 2027683939840
InnoDB: Doing recovery: scanned up to log sequence number 2027689182720
InnoDB: Doing recovery: scanned up to log sequence number 2027694425600
InnoDB: Doing recovery: scanned up to log sequence number 2027699668480
InnoDB: Doing recovery: scanned up to log sequence number 2027704911360
InnoDB: Doing recovery: scanned up to log sequence number 2027710154240
InnoDB: Doing recovery: scanned up to log sequence number 2027715397120
InnoDB: Doing recovery: scanned up to log sequence number 2027720640000
InnoDB: Doing recovery: scanned up to log sequence number 2027725882880
InnoDB: Doing recovery: scanned up to log sequence number 2027731125760
InnoDB: Doing recovery: scanned up to log sequence number 2027736368640
InnoDB: Doing recovery: scanned up to log sequence number 2027741611520
InnoDB: Doing recovery: scanned up to log sequence number 2027746854400
InnoDB: Doing recovery: scanned up to log sequence number 2027752097280
InnoDB: Doing recovery: scanned up to log sequence number 2027757340160
InnoDB: Doing recovery: scanned up to log sequence number 2027762583040
InnoDB: Doing recovery: scanned up to log sequence number 2027767825920
InnoDB: Doing recovery: scanned up to log sequence number 2027773068800
InnoDB: Doing recovery: scanned up to log sequence number 2027778311680
InnoDB: Doing recovery: scanned up to log sequence number 2027783554560
InnoDB: Doing recovery: scanned up to log sequence number 2027788797440
InnoDB: Doing recovery: scanned up to log sequence number 2027794040320
InnoDB: Doing recovery: scanned up to log sequence number 2027799283200
InnoDB: Doing recovery: scanned up to log sequence number 2027804526080
InnoDB: Doing recovery: scanned up to log sequence number 2027809768960
InnoDB: Doing recovery: scanned up to log sequence number 2027815011840
InnoDB: Doing recovery: scanned up to log sequence number 2027820254720
InnoDB: Doing recovery: scanned up to log sequence number 2027825497600
InnoDB: Doing recovery: scanned up to log sequence number 2027830740480
InnoDB: Doing recovery: scanned up to log sequence number 2027835983360
InnoDB: Doing recovery: scanned up to log sequence number 2027841226240
InnoDB: Doing recovery: scanned up to log sequence number 2027846469120
InnoDB: Doing recovery: scanned up to log sequence number 2027851712000
InnoDB: Doing recovery: scanned up to log sequence number 2027856954880
InnoDB: Doing recovery: scanned up to log sequence number 2027862197760
InnoDB: Doing recovery: scanned up to log sequence number 2027867440640
InnoDB: Doing recovery: scanned up to log sequence number 2027872683520
InnoDB: Doing recovery: scanned up to log sequence number 2027877926400
InnoDB: Doing recovery: scanned up to log sequence number 2027883169280
InnoDB: Doing recovery: scanned up to log sequence number 2027888412160
InnoDB: Doing recovery: scanned up to log sequence number 2027893655040
InnoDB: Doing recovery: scanned up to log sequence number 2027898897920
InnoDB: Doing recovery: scanned up to log sequence number 2027904140800
InnoDB: Doing recovery: scanned up to log sequence number 2027909383680
InnoDB: Doing recovery: scanned up to log sequence number 2027914626560
InnoDB: Doing recovery: scanned up to log sequence number 2027919869440
InnoDB: Doing recovery: scanned up to log sequence number 2027925112320
InnoDB: Doing recovery: scanned up to log sequence number 2027930355200
InnoDB: Doing recovery: scanned up to log sequence number 2027935598080
InnoDB: Doing recovery: scanned up to log sequence number 2027940840960
InnoDB: Doing recovery: scanned up to log sequence number 2027946083840
InnoDB: Doing recovery: scanned up to log sequence number 2027951326720
InnoDB: Doing recovery: scanned up to log sequence number 2027956569600
InnoDB: Doing recovery: scanned up to log sequence number 2027961812480
InnoDB: Doing recovery: scanned up to log sequence number 2027967055360
InnoDB: Doing recovery: scanned up to log sequence number 2027972298240
InnoDB: Doing recovery: scanned up to log sequence number 2027977541120
InnoDB: Doing recovery: scanned up to log sequence number 2027982784000
InnoDB: Doing recovery: scanned up to log sequence number 2027988026880
InnoDB: Doing recovery: scanned up to log sequence number 2027993269760
InnoDB: Doing recovery: scanned up to log sequence number 2027998512640
InnoDB: Doing recovery: scanned up to log sequence number 2028003755520
InnoDB: Doing recovery: scanned up to log sequence number 2028008998400
InnoDB: Doing recovery: scanned up to log sequence number 2028011766392
InnoDB: Transaction 35DA5A01 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 35DA5C00
120221  3:54:15  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 120221  3:54:52  InnoDB: Assertion failure in thread 1138456896 in file log/log0recv.c line 1216
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)
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.
120221  3:54:52 - 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=104857600
read_buffer_size=1048576
max_used_connections=0
max_threads=3200
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3732150 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 0x80000
/u01/mysql/libexec/mysqld(my_print_stacktrace+0x35)[0x884b95]
/u01/mysql/libexec/mysqld(handle_segfault+0x31d)[0x5bcfcd]
/lib64/libpthread.so.0[0x3453e0e7c0]
/lib64/libc.so.6(gsignal+0x35)[0x3453630265]
/lib64/libc.so.6(abort+0x110)[0x3453631d10]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab326a502]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab326b88d]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab320e355]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab3231d7d]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab32c1638]
/lib64/libpthread.so.0[0x3453e064a7]
/lib64/libc.so.6(clone+0x6d)[0x34536d3c2d]
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.
120221 03:54:52 mysqld_safe mysqld from pid file /u01/mysql/run/mysqld.pid ended
120221 04:10:27 mysqld_safe Starting mysqld daemon with databases from /u01/mysql/data
120221  4:10:27 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120221  4:10:27 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120221  4:10:27 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
120221  4:10:30  InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 2027636753953
120221  4:10:31  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
120221  4:10:31  InnoDB: Warning: allocated tablespace 3954, old maximum was 0
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2027641996800
InnoDB: Doing recovery: scanned up to log sequence number 2027647239680
InnoDB: Doing recovery: scanned up to log sequence number 2027652482560
InnoDB: Doing recovery: scanned up to log sequence number 2027657725440
InnoDB: Doing recovery: scanned up to log sequence number 2027662968320
InnoDB: Doing recovery: scanned up to log sequence number 2027668211200
InnoDB: Doing recovery: scanned up to log sequence number 2027673454080
InnoDB: Doing recovery: scanned up to log sequence number 2027678696960
InnoDB: Doing recovery: scanned up to log sequence number 2027683939840
InnoDB: Doing recovery: scanned up to log sequence number 2027689182720
InnoDB: Doing recovery: scanned up to log sequence number 2027694425600
InnoDB: Doing recovery: scanned up to log sequence number 2027699668480
InnoDB: Doing recovery: scanned up to log sequence number 2027704911360
InnoDB: Doing recovery: scanned up to log sequence number 2027710154240
InnoDB: Doing recovery: scanned up to log sequence number 2027715397120
InnoDB: Doing recovery: scanned up to log sequence number 2027720640000
InnoDB: Doing recovery: scanned up to log sequence number 2027725882880
InnoDB: Doing recovery: scanned up to log sequence number 2027731125760
InnoDB: Doing recovery: scanned up to log sequence number 2027736368640
InnoDB: Doing recovery: scanned up to log sequence number 2027741611520
InnoDB: Doing recovery: scanned up to log sequence number 2027746854400
InnoDB: Doing recovery: scanned up to log sequence number 2027752097280
InnoDB: Doing recovery: scanned up to log sequence number 2027757340160
InnoDB: Doing recovery: scanned up to log sequence number 2027762583040
InnoDB: Doing recovery: scanned up to log sequence number 2027767825920
InnoDB: Doing recovery: scanned up to log sequence number 2027773068800
InnoDB: Doing recovery: scanned up to log sequence number 2027778311680
InnoDB: Doing recovery: scanned up to log sequence number 2027783554560
InnoDB: Doing recovery: scanned up to log sequence number 2027788797440
InnoDB: Doing recovery: scanned up to log sequence number 2027794040320
InnoDB: Doing recovery: scanned up to log sequence number 2027799283200
InnoDB: Doing recovery: scanned up to log sequence number 2027804526080
InnoDB: Doing recovery: scanned up to log sequence number 2027809768960
InnoDB: Doing recovery: scanned up to log sequence number 2027815011840
InnoDB: Doing recovery: scanned up to log sequence number 2027820254720
InnoDB: Doing recovery: scanned up to log sequence number 2027825497600
InnoDB: Doing recovery: scanned up to log sequence number 2027830740480
InnoDB: Doing recovery: scanned up to log sequence number 2027835983360
InnoDB: Doing recovery: scanned up to log sequence number 2027841226240
InnoDB: Doing recovery: scanned up to log sequence number 2027846469120
InnoDB: Doing recovery: scanned up to log sequence number 2027851712000
InnoDB: Doing recovery: scanned up to log sequence number 2027856954880
InnoDB: Doing recovery: scanned up to log sequence number 2027862197760
InnoDB: Doing recovery: scanned up to log sequence number 2027867440640
InnoDB: Doing recovery: scanned up to log sequence number 2027872683520
InnoDB: Doing recovery: scanned up to log sequence number 2027877926400
InnoDB: Doing recovery: scanned up to log sequence number 2027883169280
InnoDB: Doing recovery: scanned up to log sequence number 2027888412160
InnoDB: Doing recovery: scanned up to log sequence number 2027893655040
InnoDB: Doing recovery: scanned up to log sequence number 2027898897920
InnoDB: Doing recovery: scanned up to log sequence number 2027904140800
InnoDB: Doing recovery: scanned up to log sequence number 2027909383680
InnoDB: Doing recovery: scanned up to log sequence number 2027914626560
InnoDB: Doing recovery: scanned up to log sequence number 2027919869440
InnoDB: Doing recovery: scanned up to log sequence number 2027925112320
InnoDB: Doing recovery: scanned up to log sequence number 2027930355200
InnoDB: Doing recovery: scanned up to log sequence number 2027935598080
InnoDB: Doing recovery: scanned up to log sequence number 2027940840960
InnoDB: Doing recovery: scanned up to log sequence number 2027946083840
InnoDB: Doing recovery: scanned up to log sequence number 2027951326720
InnoDB: Doing recovery: scanned up to log sequence number 2027956569600
InnoDB: Doing recovery: scanned up to log sequence number 2027961812480
InnoDB: Doing recovery: scanned up to log sequence number 2027967055360
InnoDB: Doing recovery: scanned up to log sequence number 2027972298240
InnoDB: Doing recovery: scanned up to log sequence number 2027977541120
InnoDB: Doing recovery: scanned up to log sequence number 2027982784000
InnoDB: Doing recovery: scanned up to log sequence number 2027988026880
InnoDB: Doing recovery: scanned up to log sequence number 2027993269760
InnoDB: Doing recovery: scanned up to log sequence number 2027998512640
InnoDB: Doing recovery: scanned up to log sequence number 2028003755520
InnoDB: Doing recovery: scanned up to log sequence number 2028008998400
InnoDB: Doing recovery: scanned up to log sequence number 2028011766392
InnoDB: Transaction 35DA5A01 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 35DA5C00
120221  4:10:46  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 120221  4:11:22  InnoDB: Assertion failure in thread 1118558528 in file log/log0recv.c line 1216
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)
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.
120221  4:11:22 - 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=104857600
read_buffer_size=1048576
max_used_connections=0
max_threads=3200
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3732150 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 0x80000
/u01/mysql/libexec/mysqld(my_print_stacktrace+0x35)[0x884b95]
/u01/mysql/libexec/mysqld(handle_segfault+0x31d)[0x5bcfcd]
/lib64/libpthread.so.0[0x3453e0e7c0]
/lib64/libc.so.6(gsignal+0x35)[0x3453630265]
/lib64/libc.so.6(abort+0x110)[0x3453631d10]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab304f502]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab305088d]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab2ff3355]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab3016d7d]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab30a6638]
/lib64/libpthread.so.0[0x3453e064a7]
/lib64/libc.so.6(clone+0x6d)[0x34536d3c2d]
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.
120221 04:11:23 mysqld_safe mysqld from pid file /u01/mysql/run/mysqld.pid ended
120221 04:45:06 mysqld_safe Starting mysqld daemon with databases from /u01/mysql/data
120221  4:45:06 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120221  4:45:06 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120221  4:45:06 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
120221  4:45:09  InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 2027636753953
120221  4:45:10  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
120221  4:45:10  InnoDB: Warning: allocated tablespace 3954, old maximum was 0
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2027641996800
InnoDB: Doing recovery: scanned up to log sequence number 2027647239680
InnoDB: Doing recovery: scanned up to log sequence number 2027652482560
InnoDB: Doing recovery: scanned up to log sequence number 2027657725440
InnoDB: Doing recovery: scanned up to log sequence number 2027662968320
InnoDB: Doing recovery: scanned up to log sequence number 2027668211200
InnoDB: Doing recovery: scanned up to log sequence number 2027673454080
InnoDB: Doing recovery: scanned up to log sequence number 2027678696960
InnoDB: Doing recovery: scanned up to log sequence number 2027683939840
InnoDB: Doing recovery: scanned up to log sequence number 2027689182720
InnoDB: Doing recovery: scanned up to log sequence number 2027694425600
InnoDB: Doing recovery: scanned up to log sequence number 2027699668480
InnoDB: Doing recovery: scanned up to log sequence number 2027704911360
InnoDB: Doing recovery: scanned up to log sequence number 2027710154240
InnoDB: Doing recovery: scanned up to log sequence number 2027715397120
InnoDB: Doing recovery: scanned up to log sequence number 2027720640000
InnoDB: Doing recovery: scanned up to log sequence number 2027725882880
InnoDB: Doing recovery: scanned up to log sequence number 2027731125760
InnoDB: Doing recovery: scanned up to log sequence number 2027736368640
InnoDB: Doing recovery: scanned up to log sequence number 2027741611520
InnoDB: Doing recovery: scanned up to log sequence number 2027746854400
InnoDB: Doing recovery: scanned up to log sequence number 2027752097280
InnoDB: Doing recovery: scanned up to log sequence number 2027757340160
InnoDB: Doing recovery: scanned up to log sequence number 2027762583040
InnoDB: Doing recovery: scanned up to log sequence number 2027767825920
InnoDB: Doing recovery: scanned up to log sequence number 2027773068800
InnoDB: Doing recovery: scanned up to log sequence number 2027778311680
InnoDB: Doing recovery: scanned up to log sequence number 2027783554560
InnoDB: Doing recovery: scanned up to log sequence number 2027788797440
InnoDB: Doing recovery: scanned up to log sequence number 2027794040320
InnoDB: Doing recovery: scanned up to log sequence number 2027799283200
InnoDB: Doing recovery: scanned up to log sequence number 2027804526080
InnoDB: Doing recovery: scanned up to log sequence number 2027809768960
InnoDB: Doing recovery: scanned up to log sequence number 2027815011840
InnoDB: Doing recovery: scanned up to log sequence number 2027820254720
InnoDB: Doing recovery: scanned up to log sequence number 2027825497600
InnoDB: Doing recovery: scanned up to log sequence number 2027830740480
InnoDB: Doing recovery: scanned up to log sequence number 2027835983360
InnoDB: Doing recovery: scanned up to log sequence number 2027841226240
InnoDB: Doing recovery: scanned up to log sequence number 2027846469120
InnoDB: Doing recovery: scanned up to log sequence number 2027851712000
InnoDB: Doing recovery: scanned up to log sequence number 2027856954880
InnoDB: Doing recovery: scanned up to log sequence number 2027862197760
InnoDB: Doing recovery: scanned up to log sequence number 2027867440640
InnoDB: Doing recovery: scanned up to log sequence number 2027872683520
InnoDB: Doing recovery: scanned up to log sequence number 2027877926400
InnoDB: Doing recovery: scanned up to log sequence number 2027883169280
InnoDB: Doing recovery: scanned up to log sequence number 2027888412160
InnoDB: Doing recovery: scanned up to log sequence number 2027893655040
InnoDB: Doing recovery: scanned up to log sequence number 2027898897920
InnoDB: Doing recovery: scanned up to log sequence number 2027904140800
InnoDB: Doing recovery: scanned up to log sequence number 2027909383680
InnoDB: Doing recovery: scanned up to log sequence number 2027914626560
InnoDB: Doing recovery: scanned up to log sequence number 2027919869440
InnoDB: Doing recovery: scanned up to log sequence number 2027925112320
InnoDB: Doing recovery: scanned up to log sequence number 2027930355200
InnoDB: Doing recovery: scanned up to log sequence number 2027935598080
InnoDB: Doing recovery: scanned up to log sequence number 2027940840960
InnoDB: Doing recovery: scanned up to log sequence number 2027946083840
InnoDB: Doing recovery: scanned up to log sequence number 2027951326720
InnoDB: Doing recovery: scanned up to log sequence number 2027956569600
InnoDB: Doing recovery: scanned up to log sequence number 2027961812480
InnoDB: Doing recovery: scanned up to log sequence number 2027967055360
InnoDB: Doing recovery: scanned up to log sequence number 2027972298240
InnoDB: Doing recovery: scanned up to log sequence number 2027977541120
InnoDB: Doing recovery: scanned up to log sequence number 2027982784000
InnoDB: Doing recovery: scanned up to log sequence number 2027988026880
InnoDB: Doing recovery: scanned up to log sequence number 2027993269760
InnoDB: Doing recovery: scanned up to log sequence number 2027998512640
InnoDB: Doing recovery: scanned up to log sequence number 2028003755520
InnoDB: Doing recovery: scanned up to log sequence number 2028008998400
InnoDB: Doing recovery: scanned up to log sequence number 2028011766392
InnoDB: Transaction 35DA5A01 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 35DA5C00
120221  4:45:25  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 120221  4:46:01  InnoDB: Assertion failure in thread 1117927744 in file log/log0recv.c line 1216
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)
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.
120221  4:46:01 - 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=104857600
read_buffer_size=1048576
max_used_connections=0
max_threads=3200
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3732150 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 0x80000
/u01/mysql/libexec/mysqld(my_print_stacktrace+0x35)[0x884b95]
/u01/mysql/libexec/mysqld(handle_segfault+0x31d)[0x5bcfcd]
/lib64/libpthread.so.0[0x3453e0e7c0]
/lib64/libc.so.6(gsignal+0x35)[0x3453630265]
/lib64/libc.so.6(abort+0x110)[0x3453631d10]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab304f502]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab305088d]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab2ff3355]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab3016d7d]
/u01/mysql/lib/mysql/plugin/ha_innodb_plugin.so[0x2aaab30a6638]
/lib64/libpthread.so.0[0x3453e064a7]
/lib64/libc.so.6(clone+0x6d)[0x34536d3c2d]
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.
120221 04:46:01 mysqld_safe mysqld from pid file /u01/mysql/run/mysqld.pid ended
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
120221 13:07:12  InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 2027636753953
120221 13:07:13  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
120221 13:07:13  InnoDB: Warning: allocated tablespace 3954, old maximum was 0
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2027641996800
InnoDB: Doing recovery: scanned up to log sequence number 2027647239680
InnoDB: Doing recovery: scanned up to log sequence number 2027652482560
InnoDB: Doing recovery: scanned up to log sequence number 2027657725440
InnoDB: Doing recovery: scanned up to log sequence number 2027662968320
InnoDB: Doing recovery: scanned up to log sequence number 2027668211200
InnoDB: Doing recovery: scanned up to log sequence number 2027673454080
InnoDB: Doing recovery: scanned up to log sequence number 2027678696960
InnoDB: Doing recovery: scanned up to log sequence number 2027683939840
InnoDB: Doing recovery: scanned up to log sequence number 2027689182720
InnoDB: Doing recovery: scanned up to log sequence number 2027694425600
InnoDB: Doing recovery: scanned up to log sequence number 2027699668480
InnoDB: Doing recovery: scanned up to log sequence number 2027704911360
InnoDB: Doing recovery: scanned up to log sequence number 2027710154240
InnoDB: Doing recovery: scanned up to log sequence number 2027715397120
InnoDB: Doing recovery: scanned up to log sequence number 2027720640000
InnoDB: Doing recovery: scanned up to log sequence number 2027725882880
InnoDB: Doing recovery: scanned up to log sequence number 2027731125760
InnoDB: Doing recovery: scanned up to log sequence number 2027736368640
InnoDB: Doing recovery: scanned up to log sequence number 2027741611520
InnoDB: Doing recovery: scanned up to log sequence number 2027746854400
InnoDB: Doing recovery: scanned up to log sequence number 2027752097280
InnoDB: Doing recovery: scanned up to log sequence number 2027757340160
InnoDB: Doing recovery: scanned up to log sequence number 2027762583040
InnoDB: Doing recovery: scanned up to log sequence number 2027767825920
InnoDB: Doing recovery: scanned up to log sequence number 2027773068800
InnoDB: Doing recovery: scanned up to log sequence number 2027778311680
InnoDB: Doing recovery: scanned up to log sequence number 2027783554560
InnoDB: Doing recovery: scanned up to log sequence number 2027788797440
InnoDB: Doing recovery: scanned up to log sequence number 2027794040320
InnoDB: Doing recovery: scanned up to log sequence number 2027799283200
InnoDB: Doing recovery: scanned up to log sequence number 2027804526080
InnoDB: Doing recovery: scanned up to log sequence number 2027809768960
InnoDB: Doing recovery: scanned up to log sequence number 2027815011840
InnoDB: Doing recovery: scanned up to log sequence number 2027820254720
InnoDB: Doing recovery: scanned up to log sequence number 2027825497600
InnoDB: Doing recovery: scanned up to log sequence number 2027830740480
InnoDB: Doing recovery: scanned up to log sequence number 2027835983360
InnoDB: Doing recovery: scanned up to log sequence number 2027841226240
InnoDB: Doing recovery: scanned up to log sequence number 2027846469120
InnoDB: Doing recovery: scanned up to log sequence number 2027851712000
InnoDB: Doing recovery: scanned up to log sequence number 2027856954880
InnoDB: Doing recovery: scanned up to log sequence number 2027862197760
InnoDB: Doing recovery: scanned up to log sequence number 2027867440640
InnoDB: Doing recovery: scanned up to log sequence number 2027872683520
InnoDB: Doing recovery: scanned up to log sequence number 2027877926400
InnoDB: Doing recovery: scanned up to log sequence number 2027883169280
InnoDB: Doing recovery: scanned up to log sequence number 2027888412160
InnoDB: Doing recovery: scanned up to log sequence number 2027893655040
InnoDB: Doing recovery: scanned up to log sequence number 2027898897920
InnoDB: Doing recovery: scanned up to log sequence number 2027904140800
InnoDB: Doing recovery: scanned up to log sequence number 2027909383680
InnoDB: Doing recovery: scanned up to log sequence number 2027914626560
InnoDB: Doing recovery: scanned up to log sequence number 2027919869440
InnoDB: Doing recovery: scanned up to log sequence number 2027925112320
InnoDB: Doing recovery: scanned up to log sequence number 2027930355200
InnoDB: Doing recovery: scanned up to log sequence number 2027935598080
InnoDB: Doing recovery: scanned up to log sequence number 2027940840960
InnoDB: Doing recovery: scanned up to log sequence number 2027946083840
InnoDB: Doing recovery: scanned up to log sequence number 2027951326720
InnoDB: Doing recovery: scanned up to log sequence number 2027956569600
InnoDB: Doing recovery: scanned up to log sequence number 2027961812480
InnoDB: Doing recovery: scanned up to log sequence number 2027967055360
InnoDB: Doing recovery: scanned up to log sequence number 2027972298240
InnoDB: Doing recovery: scanned up to log sequence number 2027977541120
InnoDB: Doing recovery: scanned up to log sequence number 2027982784000
InnoDB: Doing recovery: scanned up to log sequence number 2027988026880
InnoDB: Doing recovery: scanned up to log sequence number 2027993269760
InnoDB: Doing recovery: scanned up to log sequence number 2027998512640
InnoDB: Doing recovery: scanned up to log sequence number 2028003755520
InnoDB: Doing recovery: scanned up to log sequence number 2028008998400
InnoDB: Doing recovery: scanned up to log sequence number 2028011766392
InnoDB: Transaction 35DA5A01 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 35DA5C00
120221 13:07:29  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 120221 13:08:07  InnoDB: Assertion failure in thread 1122662720 in file log/log0recv.c line 1216
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)
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.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
120221 13:20:47  InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 2027636753953
120221 13:20:47  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
120221 13:20:47  InnoDB: Warning: allocated tablespace 3954, old maximum was 0
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2027641996800
InnoDB: Doing recovery: scanned up to log sequence number 2027647239680
InnoDB: Doing recovery: scanned up to log sequence number 2027652482560
InnoDB: Doing recovery: scanned up to log sequence number 2027657725440
InnoDB: Doing recovery: scanned up to log sequence number 2027662968320
InnoDB: Doing recovery: scanned up to log sequence number 2027668211200
InnoDB: Doing recovery: scanned up to log sequence number 2027673454080
InnoDB: Doing recovery: scanned up to log sequence number 2027678696960
InnoDB: Doing recovery: scanned up to log sequence number 2027683939840
InnoDB: Doing recovery: scanned up to log sequence number 2027689182720
InnoDB: Doing recovery: scanned up to log sequence number 2027694425600
InnoDB: Doing recovery: scanned up to log sequence number 2027699668480
InnoDB: Doing recovery: scanned up to log sequence number 2027704911360
InnoDB: Doing recovery: scanned up to log sequence number 2027710154240
InnoDB: Doing recovery: scanned up to log sequence number 2027715397120
InnoDB: Doing recovery: scanned up to log sequence number 2027720640000
InnoDB: Doing recovery: scanned up to log sequence number 2027725882880
InnoDB: Doing recovery: scanned up to log sequence number 2027731125760
InnoDB: Doing recovery: scanned up to log sequence number 2027736368640
InnoDB: Doing recovery: scanned up to log sequence number 2027741611520
InnoDB: Doing recovery: scanned up to log sequence number 2027746854400
InnoDB: Doing recovery: scanned up to log sequence number 2027752097280
InnoDB: Doing recovery: scanned up to log sequence number 2027757340160
InnoDB: Doing recovery: scanned up to log sequence number 2027762583040
InnoDB: Doing recovery: scanned up to log sequence number 2027767825920
InnoDB: Doing recovery: scanned up to log sequence number 2027773068800
InnoDB: Doing recovery: scanned up to log sequence number 2027778311680
InnoDB: Doing recovery: scanned up to log sequence number 2027783554560
InnoDB: Doing recovery: scanned up to log sequence number 2027788797440
InnoDB: Doing recovery: scanned up to log sequence number 2027794040320
InnoDB: Doing recovery: scanned up to log sequence number 2027799283200
InnoDB: Doing recovery: scanned up to log sequence number 2027804526080
InnoDB: Doing recovery: scanned up to log sequence number 2027809768960
InnoDB: Doing recovery: scanned up to log sequence number 2027815011840
InnoDB: Doing recovery: scanned up to log sequence number 2027820254720
InnoDB: Doing recovery: scanned up to log sequence number 2027825497600
InnoDB: Doing recovery: scanned up to log sequence number 2027830740480
InnoDB: Doing recovery: scanned up to log sequence number 2027835983360
InnoDB: Doing recovery: scanned up to log sequence number 2027841226240
InnoDB: Doing recovery: scanned up to log sequence number 2027846469120
InnoDB: Doing recovery: scanned up to log sequence number 2027851712000
InnoDB: Doing recovery: scanned up to log sequence number 2027856954880
InnoDB: Doing recovery: scanned up to log sequence number 2027862197760
InnoDB: Doing recovery: scanned up to log sequence number 2027867440640
InnoDB: Doing recovery: scanned up to log sequence number 2027872683520
InnoDB: Doing recovery: scanned up to log sequence number 2027877926400
InnoDB: Doing recovery: scanned up to log sequence number 2027883169280
InnoDB: Doing recovery: scanned up to log sequence number 2027888412160
InnoDB: Doing recovery: scanned up to log sequence number 2027893655040
InnoDB: Doing recovery: scanned up to log sequence number 2027898897920
InnoDB: Doing recovery: scanned up to log sequence number 2027904140800
InnoDB: Doing recovery: scanned up to log sequence number 2027909383680
InnoDB: Doing recovery: scanned up to log sequence number 2027914626560
InnoDB: Doing recovery: scanned up to log sequence number 2027919869440
InnoDB: Doing recovery: scanned up to log sequence number 2027925112320
InnoDB: Doing recovery: scanned up to log sequence number 2027930355200
InnoDB: Doing recovery: scanned up to log sequence number 2027935598080
InnoDB: Doing recovery: scanned up to log sequence number 2027940840960
InnoDB: Doing recovery: scanned up to log sequence number 2027946083840
InnoDB: Doing recovery: scanned up to log sequence number 2027951326720
InnoDB: Doing recovery: scanned up to log sequence number 2027956569600
InnoDB: Doing recovery: scanned up to log sequence number 2027961812480
InnoDB: Doing recovery: scanned up to log sequence number 2027967055360
InnoDB: Doing recovery: scanned up to log sequence number 2027972298240
InnoDB: Doing recovery: scanned up to log sequence number 2027977541120
InnoDB: Doing recovery: scanned up to log sequence number 2027982784000
InnoDB: Doing recovery: scanned up to log sequence number 2027988026880
InnoDB: Doing recovery: scanned up to log sequence number 2027993269760
InnoDB: Doing recovery: scanned up to log sequence number 2027998512640
InnoDB: Doing recovery: scanned up to log sequence number 2028003755520
InnoDB: Doing recovery: scanned up to log sequence number 2028008998400
InnoDB: Doing recovery: scanned up to log sequence number 2028011766392
InnoDB: Transaction 35DA5A01 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 35DA5C00
120221 13:21:02  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 120221 13:21:38  InnoDB: Assertion failure in thread 1129695552 in file log/log0recv.c line 1216
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)
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.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
120221 13:22:19  InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 2027636753953
120221 13:22:20  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
120221 13:22:20  InnoDB: Warning: allocated tablespace 3954, old maximum was 0
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2027641996800
InnoDB: Doing recovery: scanned up to log sequence number 2027647239680
InnoDB: Doing recovery: scanned up to log sequence number 2027652482560
InnoDB: Doing recovery: scanned up to log sequence number 2027657725440
InnoDB: Doing recovery: scanned up to log sequence number 2027662968320
InnoDB: Doing recovery: scanned up to log sequence number 2027668211200
InnoDB: Doing recovery: scanned up to log sequence number 2027673454080
InnoDB: Doing recovery: scanned up to log sequence number 2027678696960
InnoDB: Doing recovery: scanned up to log sequence number 2027683939840
InnoDB: Doing recovery: scanned up to log sequence number 2027689182720
InnoDB: Doing recovery: scanned up to log sequence number 2027694425600
InnoDB: Doing recovery: scanned up to log sequence number 2027699668480
InnoDB: Doing recovery: scanned up to log sequence number 2027704911360
InnoDB: Doing recovery: scanned up to log sequence number 2027710154240
InnoDB: Doing recovery: scanned up to log sequence number 2027715397120
InnoDB: Doing recovery: scanned up to log sequence number 2027720640000
InnoDB: Doing recovery: scanned up to log sequence number 2027725882880
InnoDB: Doing recovery: scanned up to log sequence number 2027731125760
InnoDB: Doing recovery: scanned up to log sequence number 2027736368640
InnoDB: Doing recovery: scanned up to log sequence number 2027741611520
InnoDB: Doing recovery: scanned up to log sequence number 2027746854400
InnoDB: Doing recovery: scanned up to log sequence number 2027752097280
InnoDB: Doing recovery: scanned up to log sequence number 2027757340160
InnoDB: Doing recovery: scanned up to log sequence number 2027762583040
InnoDB: Doing recovery: scanned up to log sequence number 2027767825920
InnoDB: Doing recovery: scanned up to log sequence number 2027773068800
InnoDB: Doing recovery: scanned up to log sequence number 2027778311680
InnoDB: Doing recovery: scanned up to log sequence number 2027783554560
InnoDB: Doing recovery: scanned up to log sequence number 2027788797440
InnoDB: Doing recovery: scanned up to log sequence number 2027794040320
InnoDB: Doing recovery: scanned up to log sequence number 2027799283200
InnoDB: Doing recovery: scanned up to log sequence number 2027804526080
InnoDB: Doing recovery: scanned up to log sequence number 2027809768960
InnoDB: Doing recovery: scanned up to log sequence number 2027815011840
InnoDB: Doing recovery: scanned up to log sequence number 2027820254720
InnoDB: Doing recovery: scanned up to log sequence number 2027825497600
InnoDB: Doing recovery: scanned up to log sequence number 2027830740480
InnoDB: Doing recovery: scanned up to log sequence number 2027835983360
InnoDB: Doing recovery: scanned up to log sequence number 2027841226240
InnoDB: Doing recovery: scanned up to log sequence number 2027846469120
InnoDB: Doing recovery: scanned up to log sequence number 2027851712000
InnoDB: Doing recovery: scanned up to log sequence number 2027856954880
InnoDB: Doing recovery: scanned up to log sequence number 2027862197760
InnoDB: Doing recovery: scanned up to log sequence number 2027867440640
InnoDB: Doing recovery: scanned up to log sequence number 2027872683520
InnoDB: Doing recovery: scanned up to log sequence number 2027877926400
InnoDB: Doing recovery: scanned up to log sequence number 2027883169280
InnoDB: Doing recovery: scanned up to log sequence number 2027888412160
InnoDB: Doing recovery: scanned up to log sequence number 2027893655040
InnoDB: Doing recovery: scanned up to log sequence number 2027898897920
InnoDB: Doing recovery: scanned up to log sequence number 2027904140800
InnoDB: Doing recovery: scanned up to log sequence number 2027909383680
InnoDB: Doing recovery: scanned up to log sequence number 2027914626560
InnoDB: Doing recovery: scanned up to log sequence number 2027919869440
InnoDB: Doing recovery: scanned up to log sequence number 2027925112320
InnoDB: Doing recovery: scanned up to log sequence number 2027930355200
InnoDB: Doing recovery: scanned up to log sequence number 2027935598080
InnoDB: Doing recovery: scanned up to log sequence number 2027940840960
InnoDB: Doing recovery: scanned up to log sequence number 2027946083840
InnoDB: Doing recovery: scanned up to log sequence number 2027951326720
InnoDB: Doing recovery: scanned up to log sequence number 2027956569600
InnoDB: Doing recovery: scanned up to log sequence number 2027961812480
InnoDB: Doing recovery: scanned up to log sequence number 2027967055360
InnoDB: Doing recovery: scanned up to log sequence number 2027972298240
InnoDB: Doing recovery: scanned up to log sequence number 2027977541120
InnoDB: Doing recovery: scanned up to log sequence number 2027982784000
InnoDB: Doing recovery: scanned up to log sequence number 2027988026880
InnoDB: Doing recovery: scanned up to log sequence number 2027993269760
InnoDB: Doing recovery: scanned up to log sequence number 2027998512640
InnoDB: Doing recovery: scanned up to log sequence number 2028003755520
InnoDB: Doing recovery: scanned up to log sequence number 2028008998400
InnoDB: Doing recovery: scanned up to log sequence number 2028011766392
InnoDB: Transaction 35DA5A01 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 35DA5C00
120221 13:22:34  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 120221 13:23:11  InnoDB: Assertion failure in thread 1111939392 in file log/log0recv.c line 1216
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)
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.
No-Mysql my160137.cm6: mysql /u01/mysql/log