MySQL启动报错，120623 13:03:09 [Note] Flashcache setup error is : ioctl failed

mysql版本： Percona 5.1.56，
linux系统： CentOS release 5.5 (Final)，
内存： 16G，
CPU：8个

mysql运行好好都半年多了，突然今天服务down了，然后重新启动报错如下：
/etc/rc.d/init.d/mysqld start

120623 13:03:09 mysqld_safe Starting mysqld daemon with databases from /data/xxdata/open
120623 13:03:09 [Note] Flashcache bypass: disabled
120623 13:03:09 [Note] Flashcache setup error is : ioctl failed
120623 13:03:09 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
120623 13:03:09  InnoDB: Initializing buffer pool, size = 1000.0M
120623 13:03:09  InnoDB: Completed initialization of buffer pool
120623 13:03:09  InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 455168644024
120623 13:03:09  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...
InnoDB: Doing recovery: scanned up to log sequence number 455173886464
InnoDB: Doing recovery: scanned up to log sequence number 455175985009
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 16282 row operations to undo
InnoDB: Trx id counter is 124FED00
120623 13:03:10  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 995413259, file name ./mysql-bin.000570
InnoDB: Starting in background the rollback of uncommitted transactions
120623 13:03:11  InnoDB: Rolling back trx with id 124FEB4C, 16282 rows to undo
InnoDB: Progress in percents: 1120623 13:03:11 Percona XtraDB () 1.0.15-12.5 started; log sequence number 455175985009
120623 13:03:11 [Note] Recovering after a crash using mysql-bin
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24120623 13:03:11  InnoDB: Assertion failure in thread 1198418240 in file fsp/fsp0fsp.c line 1772
InnoDB: Failing assertion: frag_n_used > 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to .
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-innodb-recovery.html
InnoDB: about forcing recovery.
120623 13:03:11 - 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=67108864
read_buffer_size=1048576
max_used_connections=0
max_threads=500
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1606981 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 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
[0x772974]
[0x4b19e1]
[0x61dff0]
[0x810845]
[0x7d40b0]
[0x70eb2b]
[0x70fb5c]
[0x6b647f]
[0x6b6d91]
[0x6a989b]
[0x6aac21]
[0x6902b1]
[0x67192d]
[0x6ab3f4]
[0x6ab8ee]
[0x61a0fd]
[0x7fed09]
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.
120623 13:03:11 mysqld_safe mysqld from pid file /data/mbdata/open/test-db-xxx.pid ended