Description:
After some transaction MySQL server crashed and can't start.
It exits immediately after the recovery:
InnoDB: Doing recovery: scanned up to log sequence number 10420485872640
InnoDB: Doing recovery: scanned up to log sequence number 10420489829593
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 58323 row operations to undo
InnoDB: Trx id counter is 2F7AA05A00
130807 0:29:14 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 968006821, file name /data/mysql_logs/binary_log.006505
InnoDB: Starting in background the rollback of uncommitted transactions
130807 0:32:01 InnoDB: Rolling back trx with id 2F7A36A48B, 58323 rows to undo
130807 0:32:01 InnoDB Plugin 1.0.11 started; log sequence number 10420489829593
130807 0:32:01 [Note] Event Scheduler: Loaded 0 events
130807 0:32:01 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.50-community-log' socket: '/data/mysql_data/mysql.sock' port: 3306 MySQL Community Server (GPL)
InnoDB: Progress in percents: 1InnoDB: Dump of the tablespace extent descriptor: len 40; hex 0000000000000002000180001cbe000180001d0e00000004aefeffffffffffffffffffffffffffff; asc ;
InnoDB: Serious error! InnoDB is trying to free page 109893
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
The corruption replicated to other three slaves, they have the same symptoms
How to repeat:
Don't know
