120502 11:29:21  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88598.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:21  InnoDB: Assertion failure in thread 2943531888 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:21 - 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) [0xb75ba30d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb72863d4]
[0xb7001400]
/lib/libc.so.6(abort+0x182) [0xb6d1dab2]
/usr/sbin/mysqld(+0x486851) [0xb74a5851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb7531cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb7535354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb7468b97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb746a522]
/usr/sbin/mysqld(+0x4d8e41) [0xb74f7e41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb74f864b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb74e38b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb7515e65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb750ca50]
/lib/libpthread.so.0(+0x57f0) [0xb6fe67f0]
/lib/libc.so.6(clone+0x5e) [0xb6dbf3de]
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.
120502 11:29:21 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:21  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...
120502 11:29:21  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:21  InnoDB: Started; log sequence number 0 58902
120502 11:29:21 [Note] Event Scheduler: Loaded 0 events
120502 11:29:21 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:22  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:22  InnoDB: Assertion failure in thread 2943466352 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29: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=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) [0xb75aa30d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb72763d4]
[0xb6ff1400]
/lib/libc.so.6(abort+0x182) [0xb6d0dab2]
/usr/sbin/mysqld(+0x486851) [0xb7495851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb7521cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb7525354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb7458b97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb745a522]
/usr/sbin/mysqld(+0x4d8e41) [0xb74e7e41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb74e864b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb74d38b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb7505e65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb74fca50]
/lib/libpthread.so.0(+0x57f0) [0xb6fd67f0]
/lib/libc.so.6(clone+0x5e) [0xb6daf3de]
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.
120502 11:29:22 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29: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...
120502 11:29:22  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:22  InnoDB: Started; log sequence number 0 58902
120502 11:29:22 [Note] Event Scheduler: Loaded 0 events
120502 11:29:22 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:23  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:23  InnoDB: Assertion failure in thread 2944998256 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:23 - 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) [0xb772030d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb73ec3d4]
[0xb7167400]
/lib/libc.so.6(abort+0x182) [0xb6e83ab2]
/usr/sbin/mysqld(+0x486851) [0xb760b851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb7697cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb769b354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb75ceb97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb75d0522]
/usr/sbin/mysqld(+0x4d8e41) [0xb765de41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb765e64b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb76498b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb767be65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb7672a50]
/lib/libpthread.so.0(+0x57f0) [0xb714c7f0]
/lib/libc.so.6(clone+0x5e) [0xb6f253de]
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.
120502 11:29:23 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29: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...
120502 11:29:23  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:23  InnoDB: Started; log sequence number 0 58902
120502 11:29:23 [Note] Event Scheduler: Loaded 0 events
120502 11:29:23 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:24  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24 [Note] /usr/sbin/mysqld: Normal shutdown

120502 11:29:24 [Note] Event Scheduler: Purging the queue. 0 events
120502 11:29:24  InnoDB: Starting shutdown...
120502 11:29:24  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88458.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88784.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:24  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:24  InnoDB: Assertion failure in thread 2943757168 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:24 - 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) [0xb75f130d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb72bd3d4]
[0xb7038400]
/lib/libc.so.6(abort+0x182) [0xb6d54ab2]
/usr/sbin/mysqld(+0x486851) [0xb74dc851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb7568cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb756c354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb749fb97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb74a1522]
/usr/sbin/mysqld(+0x4d8e41) [0xb752ee41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb752f64b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb751a8b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb754ce65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb7543a50]
/lib/libpthread.so.0(+0x57f0) [0xb701d7f0]
/lib/libc.so.6(clone+0x5e) [0xb6df63de]
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.
120502 11:29:25 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:25  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...
120502 11:29:25  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:25  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:25  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:25  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:25  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:25  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:25  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:25  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:25  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:25  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:25  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:25  InnoDB: Started; log sequence number 0 58902
120502 11:29:25 [Note] Event Scheduler: Loaded 0 events
120502 11:29:25 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:26  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 78218.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 78668.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 79506.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:26  InnoDB: Assertion failure in thread 2943822704 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:26 - 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) [0xb760130d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb72cd3d4]
[0xb7048400]
/lib/libc.so.6(abort+0x182) [0xb6d64ab2]
/usr/sbin/mysqld(+0x486851) [0xb74ec851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb7578cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb757c354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb74afb97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb74b1522]
/usr/sbin/mysqld(+0x4d8e41) [0xb753ee41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb753f64b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb752a8b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb755ce65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb7553a50]
/lib/libpthread.so.0(+0x57f0) [0xb702d7f0]
/lib/libc.so.6(clone+0x5e) [0xb6e063de]
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.
120502 11:29:26 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:26  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...
120502 11:29:26  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:26  InnoDB: Started; log sequence number 0 58902
120502 11:29:26 [Note] Event Scheduler: Loaded 0 events
120502 11:29:26 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:27  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:27  InnoDB: Assertion failure in thread 2944072560 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:27 - 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) [0xb763e30d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb730a3d4]
[0xb7085400]
/lib/libc.so.6(abort+0x182) [0xb6da1ab2]
/usr/sbin/mysqld(+0x486851) [0xb7529851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb75b5cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb75b9354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb74ecb97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb74ee522]
/usr/sbin/mysqld(+0x4d8e41) [0xb757be41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb757c64b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb75678b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb7599e65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb7590a50]
/lib/libpthread.so.0(+0x57f0) [0xb706a7f0]
/lib/libc.so.6(clone+0x5e) [0xb6e433de]
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.
120502 11:29:27 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:27  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...
120502 11:29:27  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:27  InnoDB: Started; log sequence number 0 58902
120502 11:29:27 [Note] Event Scheduler: Loaded 0 events
120502 11:29:27 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:28  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 78218.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 78668.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 79444.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:28  InnoDB: Assertion failure in thread 2943560560 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29: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) [0xb75c130d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb728d3d4]
[0xb7008400]
/lib/libc.so.6(abort+0x182) [0xb6d24ab2]
/usr/sbin/mysqld(+0x486851) [0xb74ac851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb7538cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb753c354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb746fb97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb7471522]
/usr/sbin/mysqld(+0x4d8e41) [0xb74fee41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb74ff64b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb74ea8b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb751ce65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb7513a50]
/lib/libpthread.so.0(+0x57f0) [0xb6fed7f0]
/lib/libc.so.6(clone+0x5e) [0xb6dc63de]
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.
120502 11:29:28 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:28  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...
120502 11:29:28  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:28  InnoDB: Started; log sequence number 0 58902
120502 11:29:28 [Note] Event Scheduler: Loaded 0 events
120502 11:29:28 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:29  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:29  InnoDB: Assertion failure in thread 2943322992 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:29 - 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) [0xb758730d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb72533d4]
[0xb6fce400]
/lib/libc.so.6(abort+0x182) [0xb6ceaab2]
/usr/sbin/mysqld(+0x486851) [0xb7472851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb74fecd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb7502354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb7435b97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb7437522]
/usr/sbin/mysqld(+0x4d8e41) [0xb74c4e41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb74c564b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb74b08b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb74e2e65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb74d9a50]
/lib/libpthread.so.0(+0x57f0) [0xb6fb37f0]
/lib/libc.so.6(clone+0x5e) [0xb6d8c3de]
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.
120502 11:29:29 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:29  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...
120502 11:29:29  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:29  InnoDB: Started; log sequence number 0 58902
120502 11:29:29 [Note] Event Scheduler: Loaded 0 events
120502 11:29:29 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:30  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 78218.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 78606.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 79056.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:30  InnoDB: Assertion failure in thread 2943560560 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:30 - 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) [0xb75c130d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb728d3d4]
[0xb7008400]
/lib/libc.so.6(abort+0x182) [0xb6d24ab2]
/usr/sbin/mysqld(+0x486851) [0xb74ac851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb7538cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb753c354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb746fb97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb7471522]
/usr/sbin/mysqld(+0x4d8e41) [0xb74fee41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb74ff64b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb74ea8b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb751ce65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb7513a50]
/lib/libpthread.so.0(+0x57f0) [0xb6fed7f0]
/lib/libc.so.6(clone+0x5e) [0xb6dc63de]
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.
120502 11:29:30 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:30  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...
120502 11:29:30  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:30  InnoDB: Started; log sequence number 0 58902
120502 11:29:30 [Note] Event Scheduler: Loaded 0 events
120502 11:29:30 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:31  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 78218.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 78668.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 78730.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:31  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:31  InnoDB: Assertion failure in thread 2943110000 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:31 - 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) [0xb755330d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb721f3d4]
[0xb6f9a400]
/lib/libc.so.6(abort+0x182) [0xb6cb6ab2]
/usr/sbin/mysqld(+0x486851) [0xb743e851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb74cacd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb74ce354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb7401b97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb7403522]
/usr/sbin/mysqld(+0x4d8e41) [0xb7490e41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb749164b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb747c8b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb74aee65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb74a5a50]
/lib/libpthread.so.0(+0x57f0) [0xb6f7f7f0]
/lib/libc.so.6(clone+0x5e) [0xb6d583de]
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.
120502 11:29:32 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:32  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...
120502 11:29:32  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:32  InnoDB: Started; log sequence number 0 58902
120502 11:29:32 [Note] Event Scheduler: Loaded 0 events
120502 11:29:32 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:33  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:33  InnoDB: Assertion failure in thread 2944879472 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:33 - 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) [0xb770330d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb73cf3d4]
[0xb714a400]
/lib/libc.so.6(abort+0x182) [0xb6e66ab2]
/usr/sbin/mysqld(+0x486851) [0xb75ee851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb767acd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb767e354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb75b1b97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb75b3522]
/usr/sbin/mysqld(+0x4d8e41) [0xb7640e41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb764164b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb762c8b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb765ee65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb7655a50]
/lib/libpthread.so.0(+0x57f0) [0xb712f7f0]
/lib/libc.so.6(clone+0x5e) [0xb6f083de]
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.
120502 11:29:33 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:33  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...
120502 11:29:33  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:33  InnoDB: Started; log sequence number 0 58902
120502 11:29:33 [Note] Event Scheduler: Loaded 0 events
120502 11:29:33 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:34  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:34  InnoDB: Assertion failure in thread 2943073136 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:34 - 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) [0xb754a30d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb72163d4]
[0xb6f91400]
/lib/libc.so.6(abort+0x182) [0xb6cadab2]
/usr/sbin/mysqld(+0x486851) [0xb7435851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb74c1cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb74c5354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb73f8b97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb73fa522]
/usr/sbin/mysqld(+0x4d8e41) [0xb7487e41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb748864b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb74738b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb74a5e65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb749ca50]
/lib/libpthread.so.0(+0x57f0) [0xb6f767f0]
/lib/libc.so.6(clone+0x5e) [0xb6d4f3de]
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.
120502 11:29:34 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:34  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...
120502 11:29:34  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:34  InnoDB: Started; log sequence number 0 58902
120502 11:29:34 [Note] Event Scheduler: Loaded 0 events
120502 11:29:34 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:35  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 78218.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 78606.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:35  InnoDB: Assertion failure in thread 2944965488 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:35 - 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) [0xb771830d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb73e43d4]
[0xb715f400]
/lib/libc.so.6(abort+0x182) [0xb6e7bab2]
/usr/sbin/mysqld(+0x486851) [0xb7603851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb768fcd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb7693354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb75c6b97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb75c8522]
/usr/sbin/mysqld(+0x4d8e41) [0xb7655e41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb765664b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb76418b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb7673e65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb766aa50]
/lib/libpthread.so.0(+0x57f0) [0xb71447f0]
/lib/libc.so.6(clone+0x5e) [0xb6f1d3de]
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.
120502 11:29:35 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:35  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...
120502 11:29:35  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:35  InnoDB: Started; log sequence number 0 58902
120502 11:29:35 [Note] Event Scheduler: Loaded 0 events
120502 11:29:35 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:36  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88148.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:36  InnoDB: Assertion failure in thread 2944633712 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:36 - 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) [0xb76c730d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb73933d4]
[0xb710e400]
/lib/libc.so.6(abort+0x182) [0xb6e2aab2]
/usr/sbin/mysqld(+0x486851) [0xb75b2851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb763ecd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb7642354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb7575b97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb7577522]
/usr/sbin/mysqld(+0x4d8e41) [0xb7604e41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb760564b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb75f08b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb7622e65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb7619a50]
/lib/libpthread.so.0(+0x57f0) [0xb70f37f0]
/lib/libc.so.6(clone+0x5e) [0xb6ecc3de]
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.
120502 11:29:36 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:36  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...
120502 11:29:36  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:36  InnoDB: Started; log sequence number 0 58902
120502 11:29:36 [Note] Event Scheduler: Loaded 0 events
120502 11:29:36 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:37  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:37  InnoDB: Assertion failure in thread 2943912816 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:37 - 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) [0xb761730d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb72e33d4]
[0xb705e400]
/lib/libc.so.6(abort+0x182) [0xb6d7aab2]
/usr/sbin/mysqld(+0x486851) [0xb7502851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb758ecd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb7592354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb74c5b97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb74c7522]
/usr/sbin/mysqld(+0x4d8e41) [0xb7554e41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb755564b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb75408b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb7572e65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb7569a50]
/lib/libpthread.so.0(+0x57f0) [0xb70437f0]
/lib/libc.so.6(clone+0x5e) [0xb6e1c3de]
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.
120502 11:29:37 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:37  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...
120502 11:29:37  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:37  InnoDB: Started; log sequence number 0 58902
120502 11:29:37 [Note] Event Scheduler: Loaded 0 events
120502 11:29:37 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:38  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 87946.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:38  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:38  InnoDB: Assertion failure in thread 2944285552 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:38 - 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) [0xb767230d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb733e3d4]
[0xb70b9400]
/lib/libc.so.6(abort+0x182) [0xb6dd5ab2]
/usr/sbin/mysqld(+0x486851) [0xb755d851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb75e9cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb75ed354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb7520b97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb7522522]
/usr/sbin/mysqld(+0x4d8e41) [0xb75afe41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb75b064b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb759b8b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb75cde65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb75c4a50]
/lib/libpthread.so.0(+0x57f0) [0xb709e7f0]
/lib/libc.so.6(clone+0x5e) [0xb6e773de]
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.
120502 11:29:39 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:39  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...
120502 11:29:39  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:39  InnoDB: Started; log sequence number 0 58902
120502 11:29:39 [Note] Event Scheduler: Loaded 0 events
120502 11:29:39 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:40  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:40  InnoDB: Assertion failure in thread 2944592752 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:40 - 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) [0xb76bd30d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb73893d4]
[0xb7104400]
/lib/libc.so.6(abort+0x182) [0xb6e20ab2]
/usr/sbin/mysqld(+0x486851) [0xb75a8851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb7634cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb7638354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb756bb97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb756d522]
/usr/sbin/mysqld(+0x4d8e41) [0xb75fae41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb75fb64b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb75e68b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb7618e65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb760fa50]
/lib/libpthread.so.0(+0x57f0) [0xb70e97f0]
/lib/libc.so.6(clone+0x5e) [0xb6ec23de]
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.
120502 11:29:40 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:40  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...
120502 11:29:40  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:40  InnoDB: Started; log sequence number 0 58902
120502 11:29:40 [Note] Event Scheduler: Loaded 0 events
120502 11:29:40 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:41  InnoDB: Error: page 20120 log sequence number 0 658569186
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 16385 log sequence number 0 481169623
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 50 log sequence number 0 7814437
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 242 log sequence number 0 994493392
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 344 log sequence number 0 658418263
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 351 log sequence number 0 658530602
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 350 log sequence number 0 658516953
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 352 log sequence number 0 658544738
InnoDB: is in the future! Current system log sequence number 0 62796.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 20121 log sequence number 0 658645863
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 355 log sequence number 0 658585255
InnoDB: is in the future! Current system log sequence number 0 65232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 354 log sequence number 0 658568922
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 356 log sequence number 0 658599464
InnoDB: is in the future! Current system log sequence number 0 69142.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 20122 log sequence number 0 658720556
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 360 log sequence number 0 658670140
InnoDB: is in the future! Current system log sequence number 0 71562.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 359 log sequence number 0 658658156
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 361 log sequence number 0 658683432
InnoDB: is in the future! Current system log sequence number 0 75472.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 353 log sequence number 0 658557666
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 357 log sequence number 0 658628725
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 358 log sequence number 0 658644755
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 362 log sequence number 0 658714279
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 363 log sequence number 0 658727107
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 364 log sequence number 0 658741091
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 365 log sequence number 0 658759099
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 366 log sequence number 0 658772574
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 367 log sequence number 0 658787240
InnoDB: is in the future! Current system log sequence number 0 77970.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 20123 log sequence number 0 658829372
InnoDB: is in the future! Current system log sequence number 0 80266.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 368 log sequence number 0 658837709
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 369 log sequence number 0 658853447
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 370 log sequence number 0 658869487
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 371 log sequence number 0 658885172
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 372 log sequence number 0 658911416
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 373 log sequence number 0 658925304
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 374 log sequence number 0 658936444
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 375 log sequence number 0 658949256
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 376 log sequence number 0 658968190
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 377 log sequence number 0 658983386
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 378 log sequence number 0 658999326
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 379 log sequence number 0 659025389
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 380 log sequence number 0 659041081
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 381 log sequence number 0 659053049
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 382 log sequence number 0 659064189
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 383 log sequence number 0 659092428
InnoDB: is in the future! Current system log sequence number 0 88396.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 20124 log sequence number 0 658884731
InnoDB: is in the future! Current system log sequence number 0 88846.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 000000000000001a00000000013e00000000018e00000004ffbfffbffffffebfbfffbeefffffffff; asc              >                          ;
InnoDB: Serious error! InnoDB is trying to free page 371
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120502 11:29:41  InnoDB: Assertion failure in thread 2943921008 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
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.
120502 11:29:41 - 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) [0xb761930d]
/usr/sbin/mysqld(handle_segfault+0x494) [0xb72e53d4]
[0xb7060400]
/lib/libc.so.6(abort+0x182) [0xb6d7cab2]
/usr/sbin/mysqld(+0x486851) [0xb7504851]
/usr/sbin/mysqld(btr_page_free_low+0x122) [0xb7590cd2]
/usr/sbin/mysqld(btr_compress+0x684) [0xb7594354]
/usr/sbin/mysqld(btr_cur_compress_if_useful+0xe7) [0xb74c7b97]
/usr/sbin/mysqld(btr_cur_pessimistic_delete+0x332) [0xb74c9522]
/usr/sbin/mysqld(+0x4d8e41) [0xb7556e41]
/usr/sbin/mysqld(row_purge_step+0x67b) [0xb755764b]
/usr/sbin/mysqld(que_run_threads+0x5b0) [0xb75428b0]
/usr/sbin/mysqld(trx_purge+0x375) [0xb7574e65]
/usr/sbin/mysqld(srv_master_thread+0xf80) [0xb756ba50]
/lib/libpthread.so.0(+0x57f0) [0xb70457f0]
/lib/libc.so.6(clone+0x5e) [0xb6e1e3de]
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.
120502 11:29:41 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:41  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...
120502 11:29:41  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Started; log sequence number 0 58902
120502 11:29:41 [Note] Event Scheduler: Loaded 0 events
120502 11:29:41 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:41 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:41  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...
120502 11:29:41  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:41  InnoDB: Started; log sequence number 0 58902
120502 11:29:41 [Note] Event Scheduler: Loaded 0 events
120502 11:29:41 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:42 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:42  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...
120502 11:29:42  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Started; log sequence number 0 58902
120502 11:29:42 [Note] Event Scheduler: Loaded 0 events
120502 11:29:42 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:42 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:42  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...
120502 11:29:42  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Started; log sequence number 0 58902
120502 11:29:42 [Note] Event Scheduler: Loaded 0 events
120502 11:29:42 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:42 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:42  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...
120502 11:29:42  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:42  InnoDB: Started; log sequence number 0 58902
120502 11:29:42 [Note] Event Scheduler: Loaded 0 events
120502 11:29:42 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:42 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:42  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...
120502 11:29:43  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Started; log sequence number 0 58902
120502 11:29:43 [Note] Event Scheduler: Loaded 0 events
120502 11:29:43 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:43 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:43  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...
120502 11:29:43  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Started; log sequence number 0 58902
120502 11:29:43 [Note] Event Scheduler: Loaded 0 events
120502 11:29:43 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:43 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:43  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...
120502 11:29:43  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Started; log sequence number 0 58902
120502 11:29:43 [Note] Event Scheduler: Loaded 0 events
120502 11:29:43 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:43 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:43  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...
120502 11:29:43  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 10 log sequence number 0 63315
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Started; log sequence number 0 58902
120502 11:29:43 [Note] Event Scheduler: Loaded 0 events
120502 11:29:43 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
120502 11:29:43 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120502 11:29:43  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...
120502 11:29:43  InnoDB: Error: page 7 log sequence number 0 63325
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 2 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 11 log sequence number 0 64548
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 5 log sequence number 0 78489
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 6 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 45 log sequence number 0 78716
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 52 log sequence number 0 993942625
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 8 log sequence number 0 62860
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 0 log sequence number 0 8270129
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 9 log sequence number 0 62914
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Error: page 12 log sequence number 0 63450
InnoDB: is in the future! Current system log sequence number 0 58902.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
120502 11:29:43  InnoDB: Started; log sequence number 0 58902
120502 11:29:43 [Note] Event Scheduler: Loaded 0 events
120502 11:29:43 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)